Chopping the Monolith
summary
Claim: isolate the frequently changing business logic (pricing) from a monolith by routing that endpoint through an api6 API Gateway to a Function-as-a-Service implementation (demo uses Azure Functions), so the monolith stays, only the hot path deploys independently. The demo shows the frontend unchanged while checkout calls are pipelined through the gateway to a JS function, reducing full releases at the cost of extra HTTP hops and coordination and preserving pragmatic deploy frequency without full microservice conversion.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:44Microservices myth: good vs bad devs
- 3:36Products vs projects in microservices
- 5:07Conway's law and team structures
- 7:41Middle manager dilemma in migration
- 9:32Why microservices fail technically
- 10:39Microservices benefits and trade-offs
- 12:02Strong module boundaries and dependencies
- 13:08Technology diversity drawback
- 14:53Independent deployment and releases
- 17:25Testing microservices assumptions
- 18:52Rules engines for quick changes
- 21:22Strangling the monolith
- 22:47When to stop chopping
- 24:14Demo setup
- 25:19Live demo: pricing engine extraction
- 32:06Summary
- 34:52Industry critique and cargo culting
- 38:44Q&A on scalability
