Crafting the Core - Why and How We Built the Core Banking System
summary
Solarisbank moves from a vendor core to an in-house payment ledger called corona, claiming event sourcing + CQRS as the core patterns and starting on MySQL and Redis before using Postgres NOTIFY then SNS/SQS for scalable messaging. The team builds a proxy that owns truth for some competencies, embraces eventual consistency then adds selective synchronous reads, and proves it: by one year after getting a second BIC the new system handles 20% of payments and 50% of new accounts in Q3, servicing tens of thousands of customers and hundreds of thousands of transfers.
AI-written summary · about
chapters (9)
- 0:00Intro
- 3:12First - the story
- 5:18What is core-banking?
- 8:40Mitigation
- 14:40Eventually consistent
- 20:44Event storming
- 24:16It was not all that smooth
- 30:12You build it, you run it
- 32:23One more thing
related talks
37mStone Bank: how a team of initially 5 (...)
55mFrom the engine to the bridge - building systems that scale
32mOutpace Your Competition: Banking Solution Thrives with Scale and Security
31mOn-core vs. virtual accounts - what you need to know today
22mBuilding a Modern Data Foundation: A Conversation with OCBC's Head of Data Architecture
30mShared Database Concurrency
45mE-commerce platform. Core build principles, problems and guidelines.
41mBuilding a Bank (with DDD, Microservices, and Autonomous Teams)