Minimum Viable Migrations (MVMs): A Path to Cloud Native EDAs
summary
Argues a practical path from monolith to cloud native by slicing migration into eight-week MVMs that each target one bounded context, using eventification (CDC, app hooks) to push domain events into AWS EventBridge and an EventBridge schema registry, and translating payloads with an anti-corruption layer so new services consume clean business events. Shows an airline migrated incrementally (multiple teams, an MVM every eight weeks) by adding .NET hooks to emit events, resulting in higher deployment frequency and successful phased cutovers.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:53Agenda
- 1:50What is agile?
- 2:54What is cloud migration?
- 4:13Why are migrations not agile?
- 6:21Minimum viable migrations
- 9:11Looks easy, right?
- 10:17EventStorming
- 12:23Eventification & ACL
- 15:39Injection strategies
- 19:55Building the MVM roadmap
- 23:04Conclusions
- 25:45Outro
related talks
22mAdopting Cloud Native EDAs - The Serverless Staircase
25mData-Driven Migration from Monoliths to Event-Driven Microservices
32mSplitting the monolith
48mMinimum Viable Architecture
58mJourney to the Cloud - a Rearchitecting Story
36mFrom VMs to Containers: Decompose and Migrate Old Applications
48mMicroMonolith
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices