Monolith 2 MicroServices Houston we've got a problem
summary
Companies fail when they treat microservices as a flip-the-switch project; claim is that success requires an atomic evolutionary steps plan: assessment, API governance, a training roadmap and cross-department involvement. Practical build shows an API gateway plus monitoring, logging and analytics, passive and active health checks, and service discovery; customers move from chaotic releases to regular cadence (example: after four years one customer reaches one release every two weeks).
AI-written summary · about
chapters (10)
- 0:00Start
- 2:12MONOLITH CONTEXT
- 4:41CASE 2
- 6:32SUPPORT TIME
- 6:57ATOMIC EVOLUTIONARY STEPS
- 7:24ASSESSMENT
- 7:59GOVERNANCE
- 8:27BUILDING BLOCKS
- 10:21AGILE
- 11:35EXAMPLE
related talks
36mDo Proper Monoliths before You Do Microservices!
44mMicroservices - How to create problems by solving problems?
47mMicroservices? Monoliths? An Annoying Discussion!
47mBreak Up the Monolith: Testing Microservices
06mDo proper monoliths before you do microservices!
37mEvolutionary Architecture & Microservices
43mGo micro with Microservices
01h 01mMicroservices Gone Wrong