Chopping the monolith
summary
Argument: only a few hotspots need independent deployment, so use serverless as a middle path between rule engines and full microservices. Demonstrates replacing a pricing port in a Spring Boot/Kotlin monolith with a JavaScript function deployed to Azure Functions, routed through Apache APISIX (etcd config) while MariaDB and the monolith stay unchanged. Claims microservice payoff appears around 70 developers. Demo shows live code changes on serverless without redeploying the monolith.
AI-written summary · about
chapters (13)
- 0:00Monolith challenges
- 1:04Microservices hype vs reality
- 4:00Conway’s law and org structure
- 6:29Middle managers in change
- 9:45Microservices in legacy orgs
- 11:09Microservices benefits
- 14:24Independent deployment cycles
- 17:42Frequently changing code
- 20:57Strangling the monolith
- 22:43Demo setup
- 24:29Live demo pricing engine
- 30:54Summary
- 31:34Q&A
