Pragmatic Microservices
summary
Large systems tend to evolve into microservices, not start there: eBay moves from a single DLL of 3.4 million lines to a polyglot service landscape over years, sometimes seven. Success requires concrete prerequisites—continuous delivery, cross‑functional service teams, detailed monitoring—and a pilot: build a pilot vertical experience, write tests, create a seam, wall it behind an interface, then extract and repeat. Avoid anti‑patterns like mega services, leaky abstractions and shared persistence, which wrecks encapsulation and caused early SOA failures.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:16Architecture Evolution
- 3:22Pragmatic Evolution
- 3:49The Monolithic Application
- 5:13The Monolithic Database
- 6:53Improving the Monolith
- 12:09Prerequisites for Success
- 12:43Process Maturity: Continuous Delivery
- 14:47Organizational Maturity: Conway's Law
- 16:24Organizational Maturity: Service Teams
- 18:14Operational Maturity Monitoring
- 19:18Why Rearchitect?
- 25:10Incremental Migration
- 28:45Carving up the Monolith
- 32:33Service Anti-Patterns
- 34:25Microservices may not be for you if...
related talks
45mMicroservices: A retrospective
44mThe Yellow Brick Road: Taking Microservices Home in Large Enterprises
37mEvolutionary Architecture & Microservices
57mEmbracing Microservices
27mThe technical journey to microservices
52mMicroservices: A Utopian Mystery
47mEmbracing Microservices
52mI Have a Microservices Architecture and I Didn't Know.