Love Your Monolith
summary
Argues against ripping apart working systems and shows concrete techniques to get microservice benefits inside a monolith: enforce boundaries with psalm internal, run background work via job queues and satellite services for nonessential tasks, use infrastructure as code (Terraform, Packer, Docker Compose) to make deployments reproducible, and favor integration/acceptance tests (Codeception) over brittle unit-only suites. Claims microservices often trade simple function-call reliability for network fragility and that preserving embedded business knowledge in the monolith is usually cheaper and safer.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:40Defining the architecture
- 3:37Understanding monoliths
- 8:15Microservices vs monoliths
- 13:57Logical systems and coupling
- 25:01Building stable systems
- 33:20Flexibility and testing
- 41:32Conclusion and wrap-up
related talks
45mHow I learned to stop worrying and love the monolith
36mDo Proper Monoliths before You Do Microservices!
43mMonolith? Microservices? Who cares?
02h 29mPractical advice for building glorious monoliths
52mMy Monolith Is Really Cool
01h 01mModular Monolith Instead of Microservices: How, When and Why
42mChopping the monolith
36mIt's Simple...