Data-Driven Migration from Monoliths to Event-Driven Microservices
summary
A datadriven migration framework claims a measurable path from monolith to event-driven microservices: domain decomposition, event sourcing with 47 distinct event types, and resilience patterns that cut cascading failures by 85%. Implementation uses Apache Kafka, event store and Exxon framework, builds projections and append-only logs, and runs an incremental rollout that achieves zero downtime progressive traffic shift for a Fortune 500 retail system handling millions of daily transactions. Metrics, tools, and outcomes are concrete and repeatable.
AI-written summary · about
chapters (15)
- 0:00Introduction to Resilient by Design
- 1:26Challenges in Migrating to Microservices
- 3:34Data-Driven Migration Framework
- 4:08Domain Driven Design
- 5:17Event Sourcing Explained
- 6:15Event Driven Patterns
- 7:17Continuous Delivery and Distributed Systems
- 10:43Real-World Case Study
- 12:05Phases of Migration
- 14:11Event Schema Design
- 15:32Resilience Patterns
- 17:33Real-Time Monitoring
- 19:42Comparing Migration Methodologies
- 21:31Implementation Roadmap
- 23:50Conclusion and Final Thoughts
related talks
01h 08mEvent Driven Architecture – Enabling Microservices
24mPatterns of Evolution from Monolith to Microservices
40mFrom Monolith to Observable Microservices using DDD
47mEvent-Driven Microservices = Microservices Done Right
31mMonolith to Microservices: A Guide to Seamless Transitions
39mMicroservices: Improving Team Management with Event Driven Architecture
26mMetamorphosis: Microservices & Event-driven Architecture
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data