Modernising banking with Judo Bank
summary
Judo Bank migrates its core to Thought Machine on AWS using serverless Lambdas, Confluent Kafka, Aurora, Terraform and New Relic, moving 8,000 lending customers and a 12B loan book plus ~80,000 deposit accounts off the old platform across pilots and rehearsals that start in 2023 and complete by 2025. Compute runs ~$25k/month, API latency improves ~4x, new product time drops from 12+ months to ~4 months, and infrastructure yields zero downtime while a lean nine‑engineer team operates it.
AI-written summary · about
chapters (13)
- 0:00Introduction and welcome
- 1:11Why modernize core banking
- 2:38Modernization approaches
- 6:51Judo Bank’s transformation journey
- 10:27Building a lean engineering team
- 12:10Serverless architecture benefits
- 13:56Ensuring system resiliency
- 14:59Secure by design infrastructure
- 17:06Migration timeline and process
- 22:04Key lessons learned
- 24:12Results and business impact
- 25:40Future plans and AI initiatives
- 26:43Summary and closing
related talks
48mThe Journey of a strongly coupled Monolith into the Cloud Land
37mShaping the future of modular and composable banking solutions
18mMigrating Legacy Financial Systems to Cloud: Challenges and Best Practices
17mHow ANZ Bank is using cloud to enable digital transformation
51mMigrating a modern spring web application to serverless
41mTechnology mix: Around the serverless in 180 days
36maccelerates its modernization journey with
58mFaster, Cheaper, Greener: Pick Three