Building a Bank with Kubernetes
summary
Monzo builds its banking backend as 150 microservices on Kubernetes, running Linkerd as a daemonset on every host so each service talks to a local proxy; Cassandra stores service-owned data and Vault plus AWS KMS handle secrets. Physical rails to card schemes use IPsec tunnels and BGP to prevent split routing, Calico enforces PCI network zones, CoreOS hosts minimal signed images, and Kubernetes consolidation cuts comparable infrastructure spend to about one third.
AI-written summary · about
chapters (13)
- 0:00Start
- 5:28The Core Banking System
- 19:07Network Isolation
- 24:10Data Encryption at Rest
- 25:09Application Layer Security
- 25:54Are There any Requirements That Mandate We Have To Have Dedicated Instances
- 26:37The Security of the Containers
- 26:50Core Os
- 28:27Structured Logging
- 30:12What Was Wrong with Rabbitmq
- 32:43Monitoring
- 33:47Data Model
- 34:36Transactions
related talks
01h 03mGo & Microservices
51mMicroservices in Go
30mBuilding a Scalable, Compliant, Multi-Cloud Bank with a Service Mesh
34mFrom Monolith to Microservices with Kubernetes and Linkerd
32mLesson Learnt Running an Indian Bank on Kubernetes
41mBuilding a Bank (with DDD, Microservices, and Autonomous Teams)
23mAdopting APIs & Microservices at a Major Bank (Part 2)
19mBuilding an On-Premise Kubernetes...