💰Form3 Switches to Multi-Cloud, Avoids AWS Lock-In
UK banks can now exit AWS easily
TL;DR
Form3, a UK fintech, shifted to a multi-cloud strategy to comply with banking regulations and avoid AWS lock-in. This move uses Kubernetes and cloud-agnostic techs like NATS JetStream and CockroachDB.
Form3, a UK fintech powering account-to-account payments, ditched AWS lock-in to comply with UK banking regulations. The new architecture uses Kubernetes and cloud-agnostic techs like NATS JetStream and CockroachDB, ensuring data safety and flexibility. Form3's move is a direct response to the UK's banking regulator's 2021 statement on concentration risks in cloud providers. This shift allows UK banks to exit AWS without major disruptions, a win for regulatory compliance and operational flexibility.
Key Points
Form3's initial AWS architecture used Java, Docker, and AWS SQS for coordination.
The new architecture uses Kubernetes clusters in Google, Azure, and AWS for flexibility.
NATS JetStream, a Go-based message broker, runs across multiple nodes for reliability.
CockroachDB, a Postgres-compatible database, ensures data safety and easy migration.
Form3's multi-cloud strategy avoids AWS lock-in, aligning with UK banking regulations.
Why It Matters
Form3's multi-cloud strategy allows UK banks to comply with regulatory requirements and avoid AWS lock-in. Banks using Form3 for account-to-account payments now have the flexibility to switch cloud providers without significant changes to their tech stack. This shift impacts financial institutions relying on cloud-based payment systems, ensuring they can adapt to regulatory changes and reduce dependency on a single cloud provider.
Frequently Asked Questions
Why does this matter?
Form3's multi-cloud strategy allows UK banks to comply with regulatory requirements and avoid AWS lock-in. Banks using Form3 for account-to-account payments now have the flexibility to switch cloud providers without significant changes to their tech stack. This shift impacts financial institutions relying on cloud-based payment systems, ensuring they can adapt to regulatory changes and reduce dependency on a single cloud provider.
What happened?
Form3, a UK fintech, shifted to a multi-cloud strategy to comply with banking regulations and avoid AWS lock-in. This move uses Kubernetes and cloud-agnostic techs like NATS JetStream and CockroachDB.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,476 builders reading daily.