Chopping the monolith
summary
Argues that splitting only the frequently changing parts is better than full microservice rewrites and that a Function-as-a-Service middle path lets teams deploy business rules independently. Demonstrates extracting a pricing endpoint from a Kotlin monolith, reconfiguring an API gateway (Apache APISIX with configuration in etcd) to forward /price to an Azure Function, running via Docker Compose, and showing the live demo works with no deployment of the monolith.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:11Microservices hype debunked
- 6:58Problems with microservices adoption
- 10:38Lead time and monolith constraints
- 14:25Changing parts of the codebase
- 17:03Alternatives to microservices
- 18:30Strangling the monolith strategy
- 20:19E-commerce pricing demo intro
- 23:22Demo setup and API gateway
- 26:57Live demo of monolith chopping
- 28:49Q&A and closing remarks
