Microservices are Not Worth the Trouble!!??
summary
Argues that microservices often shift complexity rather than remove it, with benefits like independent releases and reduced handovers achievable by other means; recounts ThoughtWorks work that split a monolith into assemblies in ~one year, and another engagement that drops cycle time from 13 months → 1 day by proxying a focused service into the main app rather than full decomposition; warns of the microservices premium: heavy DevOps, monitoring, eventual consistency, funding and ops cost (one project ran ~20 languages and took five months to provision certificates) and shows the practical tradeoffs.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker setup
- 1:56Why microservices are tempting
- 4:05Complexity in distributed systems
- 8:43Debugging microservices challenges
- 10:07Outcomes matter more than tech
- 12:54Reducing team handovers
- 15:08Microservices premium explained
- 18:17When microservices fail badly
- 21:49Case study: decoupling without microservices
- 28:52Case study: breaking silos to reduce cycle time
- 37:57Top tips for better outcomes
- 40:49Conclusion and final thoughts
related talks
55mMicroservices, Where Did It All Go Wrong
44mMicroservices, Where Did It All Go Wrong
26mPros/Cons of Microservices
01h 08mWhy you should never build Microservices - and why we do it anyway
38mMicroservices, a bittersweet symphony
01h 00mMicroservices, Where Did It All Go Wrong?
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
55mIs it Time to Abandon Microservices? Modular Monoliths Rescue Your Wallet!