There and Back Again
summary
Argues measurable lessons from Red Hat and JBoss experience: microservices often just reintroduce classic distributed‑systems failures and tradeoffs; containers plus Kubernetes drive immutable deployment patterns and change operational assumptions; HTTP remains common but teams adopt gRPC and polyglot runtimes for performance; some monoliths become maintainable via the majestic monolith approach so rewind or split only with clear architecture; unit of deployment, state location and cascading failure counts remain open, and many success stories sit beside surprising failures.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:15The Map
- 3:06Monoliths
- 8:35Microservices
- 15:09Cobra
- 17:32Distributed Systems
- 20:39Emperors New Clothes
related talks
30mHow to Fail at Building Modern Microservices
57m6 Lessons I Learned on My Journey from Monolith to Microservices
01h 01mRip It Up And Start Again?
01h 03mThe Magic of Small Things - 10 Years of Microservices
24mDistant Past of Microservices
54mServices, Services, Everywhere!
57mBuilding Systems that are #neverdone
01h 03mMicroservices vs The Distributed Monolith
