Pros/Cons of Microservices
summary
Argues that micro services win when a specific bottleneck is extracted and scaled, with an example of pulling out payments (not rewriting the whole monolith) and a real-world system morphing into 20 microservices. Claims prerequisites: standardized deployment pipelines, consumer‑driven contracts, monitoring with correlation IDs, chaos‑testing and continuous delivery. Warns of cognitive complexity from mixed languages and databases, and recommends the inverse Conway maneuver—restructure teams to match bounded services before splitting.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:11Magic and silver bullets
- 3:38Decentralised Governance
- 4:22All the tools and tech!!
- 5:36Cognitive complexity
- 7:04Monitoring
- 9:50Scaling
- 10:13Design For Failure
- 12:03Reducing Risk of Release
- 16:02Replaceable Services
- 18:24So microservices?
- 19:21Conway's Law
- 21:12Continuous Delivery
- 21:46Products, not Projects
- 23:32Maturity
