Microservice Gardening
summary
Microservices require treating the landscape as a decentralized, evolving ecosystem: apply lessons from the Web and bureaucracy to prioritize loose coupling, decentralized documentation and discovery, and manage coexistence with legacy “castle” systems via the Strangler pattern. Expect many teams to pick different stacks, expect tooling gaps (only Netflix/Amazon build custom platforms), and plan for an API gardener role that curates descriptions, measures patterns (e.g., 500 of 800 services converging on a practice) and buys or composes tooling to make the diversity manageable.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:55The Kafka Method
- 9:19Franz Kafka
- 12:01The History of Bureaucracy
- 19:17Avoiding Tight Coupling
- 29:49Decentralized Documentation and Discovery
- 34:08How Can an Enterprise Adopt a Micro Services Architecture without Throwing Away some Complete Existing Architecture
- 35:30Strangler Pattern
