What has 4 years of AWS Microservices taught me?
summary
Four years of migration from a monolith with 50–60 developers and eight teams produces concrete lessons: initial setup needs significant time or a chosen invest upfront 6–9 months approach to get CI/CD, data DR, and deployment patterns right; integration with the monolith incurs real cost (two‑day release cycles slowed sprints); capability building and a capability roadmap speed future work; poor alignment breeds over‑engineering (ended up with 4–5 event buses); aim for 10–20 microservices boundaries that minimize cross‑service change.
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:43About me
- 3:41The Story we will go through today
- 5:30Monolith vs Microservice
- 8:41Technical Decisions
- 13:30LESSON 1
- 16:53End to end ownership
- 27:47Slice of Monolith
- 30:00Lesson 3: Tethered to the Monolith
- 37:58Lesson 4: Share Capabilities
- 41:04Scattergun Approach
- 42:28Capability Roadmap
- 43:44Align teams to Capabilities
- 52:05SUMMARY
related talks
57m6 Lessons I Learned on My Journey from Monolith to Microservices
41mThe six obstacles of moving to microservices and how to deal with them
45mBuilding and evolving microservices: lessons from the frontlines
43mMicroMonolith - Top anti-patterns of distributed systems
32mSplitting the monolith
35mSeven years with microservices: a critical review
48mThirty months of microservices
48mMicroMonolith