Episode 3 of The CTO Podcast dives into how Monzo, the UK neobank, rebuilt its core transaction-processing engine after hitting performance and reliability ceilings. Lucas and Luna walk through the specific architectural problem: a relational database bottleneck that capped transaction throughput at 1,000 per second during peak hours. They explain Monzo's decision to move to a custom event-sourcing model built on Apache Kafka and CockroachDB, the trade-offs of dropping ACID compliance for transactional speed, and how the engineering team handled the risk of a years-long migration without freezing product development. The episode uses Monzo's 2023-2025 re-platforming as a concrete case study in when to rewrite versus refactor, and what it takes to maintain customer trust during a core system change. Along the way, they touch on how Monzo's CTO Sujata Bhatia structured the migration into six-week phases, the unexpected operational cost of running two systems in parallel, and what other fintech CTOs can learn from Monzo's decision to build rather than buy a core banking ledger.