![]() When Stake originally started building their product, they wrote the application in Java and they wrote it fast! As with many startups, they wanted to go from concept to MVP very quickly. It’s also important that they are able to easily scale out to a global user base as their platform grows (they have over 450,000 users today) while maintaining high availability. RELATED Read the full Form3 case study Stake controls data location in multi-cloud deploymentĪs an online trading company, it’s crucial that Stake is able to provide its customers with the right data at the right time so they can make informed decisions with their money. ![]() Using CockroachDB almost feels a bit magic.” – Kevin Holditch Head of Platform Engineering, Form3 And then you have this tremendous scaling capability. You might think it’s just a simple query, but it’s actually going off to different nodes where the data is physically stored to retrieve it. “CockroachDB is doing some amazing gymnastics under the bonnet. ![]() Even with that complex multi-node, multi-cloud architecture, developers can still treat CockroachDB as if it were a single-instance Postgres database. That way, Form3 engineers can concentrate on the value add for the business, which is running their software and developing new features.Īnd they don’t have to worry about or manage how their data is distributed, because CockroachDB handles that automatically. They use the managed Kubernetes control plane offering for each vendor so that the vendor runs Kubernetes. They decided to run CockroachDB across all three cloud providers: AWS, GCP, and Azure. Given all the emerging regulations, Form3 thought there was a better solution: to not depend on any single cloud provider and run across multiple clouds at the same time. However, regulators started to ask Form3 questions about their infrastructure: What would happen if you couldn’t use AWS anymore? Is your platform portable? What if AWS has an outage? Can you run your platform in different clouds? Form3 originally selected AWS as their cloud provider and they started building their Faster Payment System (FPS) access solution on Amazon RDS for PostgreSQL which initially worked well for their needs. ![]() Form3 was founded to make this much less complex for its customers by delivering a managed payments infrastructure with a single API that helps you adhere to payment schemes wherever you do business.Īside from different payment schemes that they have to navigate, there are also different legislations Form3 must adhere to. In the payments industry, when you serve a global customer base you need to navigate different payment schemes (i.e., the sets of rules for performing payment transactions) in different countries. Why Form3 adopted a multi-cloud architecture for payments However, it can be very difficult to set up multiple cloud environments if your architecture is reliant on legacy software that wasn’t built to be cloud-native, or cloud proprietary tools that can’t run on other clouds.īelow we will discuss how three forward thinking fintech companies build on a cloud-native, distributed SQL database (CockroachDB) to guarantee resiliency, avoid an unfavorable cloud vendor lock-in scenario, and ultimately future-proof their business. One of the best approaches to ensure fault tolerance and achieve cloud portability is to run your applications across multiple clouds. Increasingly, regulatory bodies across the globe are advancing rules that require companies in important industries like fintech to employ resilient architectures that can survive severe operational disruption (outages, cyber attacks, etc). In some industries like financial services, it’s also a response to regulations. This capability helps organizations increase resilience and avoid the risks associated with cloud concentration. Not only do organizations want to build on a cloud-native foundation, but they also want to have the ability to move applications and data from one cloud computing environment (public and/or private) to another with minimal disruption – also known as cloud portability. It makes sense – building with cloud-native technologies can shorten development cycles and increase operational efficiency. Sign upĪccording to Gartner, by 2025 over 95% of new digital workloads will be deployed on cloud-native platforms. Learn how to architect for Cloud Portability.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |