Microservices Paradise: is it possible to achieve?
summary
Argues for concrete engineering rules: enforce layered services with one-way calls BFF -> flow -> stateful -> gateway, allow skipping layers but forbid lateral chatter, and name services by department-domain (eg retail_card_payments). Introduces an expert review committee, an automated office-hours process and design templates (SLA/SLO, schemas, UML). Uses a risk assessment matrix to gate reviews with risk tiers 0–3 so only high-severity changes hit the company-level committee, lower tiers stay local.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:31Communication rules
- 6:05Naming conventions
- 8:10Expert committee
- 10:40Risk assessment
- 13:29Design review process
- 14:59Summary
related talks
38mMicroservices, a bittersweet symphony
48mIT Architecture : All your micro-services are wrong PERIOD!
56mDesigning in the World of Microservices
52mMicroservices & the Inverse Conway Maneuvre
45mResponsible Microservices
44mMicroservices - How to create problems by solving problems?
16mMicroservice Challenges
48mChallenges in Implementing MicroServices