Splitting the monolith
summary
Case study of a 43-year-old mainframe migrating to microservices with a four-step approach: gain perspective (three months max of analysis), plan, pilot, and phased cutover. Goal is clear: move from 5-year releases to two releases a year. Techniques include value-stream mapping, instrumentation, Conway/reverse-Conway boundary decisions, scoring services by risk/value, and a dual-write data migration then cutover pattern; Kubernetes or off‑the‑shelf products are not magic fixes.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:59Life Insurance and Annuities
- 5:35Main Business Challenges
- 6:55Main IT Challenges
- 13:42Cataloging Technologies
- 24:33Migrating Data Paths
- 29:27Staging Teans
- 30:24Final Lessons
related talks
42mQ&A - Monolith to Microservices
52mMicroservice Migration Roadmap
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
48mMicroMonolith
39mConsidering Migrating a Monolith to Microservices?
57mSplitting Monolith Application to Microservices
31mMonolith to Microservices: A Guide to Seamless Transitions
01h 03mFrom Monolith to Microservices: Story and Practice
