Shifting gear, A Reactive Story in Banking
summary
Built a modern, reactive SEPA payment engine that replaces legacy COBOL flows and runs on Akka and Java, with a one-month initial design followed by development and production rollout. The system processes millions of payments for private and business customers, handles XML validation, clearing rules, idempotency and retries, and balances batch vs streaming flows. Key takeaways: heavy automated testing, design for event-based consistency, local indexed copies for performance, and operational monitoring for cluster bootstrap and scaling.
AI-written summary · about
chapters (7)
- 0:00Introduction to reactive banking
- 3:37Payment processing challenges
- 9:13System design and architecture
- 16:42Event-driven architecture benefits
- 25:03Reactive systems in banking
- 33:23Common reactive mistakes
- 35:48Conclusion and Q&A
related talks
14mReactive Services in practice with Webflux, Kafka and DynamoDB
01h 11mReactive Architecture Patterns Debate
44mFrom Functional to Reactive - Patterns in Domain Modeling
01h 27mReactive Oriented Architecture with Grails
49mRethinking Reactive Architectures
48mReactive for the Impatient
03mAm I only streaming? Thinking reactive
58mReactive Spring