How I learned to stop worrying and love the monolith
summary
Argues that a structured monolith lets teams start simple and later extract services with minimal rework by organizing code by feature not layer. Demos a Bookstore split into three bounded contexts (book catalog, rating, recommendation) that run first as one process then as separate services behind an API gateway, using RabbitMQ for events, Eureka for discovery, Hystrix-style circuit breaking and per-component databases. Claims most teams (≈90%) default to layered code and shows the transition working end to end.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:16Monoliths and Micro Services
- 9:07Layered Architecture
- 11:16Model Code Gap
- 12:20The Model Code Gap
- 13:12Demo
- 15:29Code Base
- 19:54Package Structure
- 20:52Context Map
- 21:12Bounded Context
- 25:59Api Gateways
- 29:35Service Discovery
- 35:19Transition from a Monolid into a Micro Service
- 37:27Structured Monolith
- 43:03Ports and Adapters Architectural Principle
related talks
46mLove Your Monolith
36mDo Proper Monoliths before You Do Microservices!
02h 29mPractical advice for building glorious monoliths
36mIt's Simple...
42mChopping the monolith
01h 03mMicroservices vs The Distributed Monolith
01h 02mBuilding that glorious monolith. And carving it too.
42mDo proper monoliths before you do microservices!