Route to microservices the epic voyage of a fintech leader
summary
Kyriba recounts moving a 17‑year Java monolith (1,800 customers, ~$100M revenue, 170 engineers) into decoupled modules using event‑storming and DDD, keeping a shared Oracle DB retained for now while extracting services; CI/CD and Docker/Kubernetes pipelines (Jenkins, JFrog, ELK) are in place. Prototypes show session sharing with Redis/Hazelcast/Ignite prototypes and an API edge using Spring Cloud gateway with Hystrix, Ribbon and Zipkin. Componentization proves effective; full DB split and finer service boundaries remain work in progress.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:45Location
- 2:19The year 2000
- 4:18What is multitenant
- 4:53Oldschool architecture
- 6:41Future is uncertain
- 7:35Go to market strategy
- 8:04Technology and product
- 9:28Growth
- 10:26Why 2012
- 14:49Lessons learned
- 15:25Where do you go
- 16:08Componentization
- 22:28Compensation
- 30:18Componentisation
- 31:26Why microservices
- 32:15Its not easy
- 32:56Its complex
- 34:12Session
- 38:22EPI Gateway
- 42:19Conclusion
related talks
29mMoving from A and B to ~150 microservices, the journey and learnings
25mFrom Millions of Customers to Petabytes of Data: A Journey to Microservices
28mThe journey from monolith to microservices
18mMicroservices Out In the Wild
35mMicroservices: A Tale of 3 Heroes
57mSplitting Monolith Application to Microservices
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
01h 07mMicroservices from the Trenches. A Guide through the Architecture, Design, Code