Designing in the World of Microservices
summary
Focuses on design rules that matter for microservices: favor autonomy of development and isolated deployment, partition by domain not tech, and enforce encapsulation so each service owns its data (avoid a shared enterprise database). Argues YAGNI and last‑responsible‑moment beat premature interfaces, warns reuse can break deployment autonomy, cites Conway’s Law and a real insurance example with thousands of tables and ~800 columns to show why bounded context and sensible granularity are essential.
AI-written summary · about
chapters (9)
- 0:00Introduction to microservices design
- 1:24Good software design principles
- 13:17SOLID principles and YAGNI
- 19:58What are microservices?
- 24:53Microservices vs monoliths and SOA
- 34:18Key microservices considerations
- 41:22Encapsulation and bounded contexts
- 47:07Practical example and data design
- 55:21Summary and Q&A
related talks
01h 01mArchitectural Principles and Practices to Build MicroServices
01h 02mDesigning Microservices
49mDDD & Microservices: At Last, Some Boundaries!
48mDesign principles to the rescue of micro-services
48mIT Architecture : All your micro-services are wrong PERIOD!
38mMicroservices, a bittersweet symphony
01h 00mPrinciples for Building MicroServices
16mMicroservices Paradise: is it possible to achieve?
