Mark Richards at DDD Europe
summary
Argues that copying a monolith across servers just duplicates capacity limits and blocks growth, using a glass-and-water demo that shows state filling CPU memory and threads until scaling fails. Proposes decomposing the app into independently deployable modules or services so each piece scales on its own, reducing contention and enabling sustained customer and store growth. Notes a small leftover integration mess after the split.
AI-written summary · about
related talks
36mDo Proper Monoliths before You Do Microservices!
02h 29mPractical advice for building glorious monoliths
01h 29mMonolithic Delivery
52mBuilding monolith applications that could scale to microservices..
39mWays out of a monolith
33mChopping the monolith
45mBuilding Monoliths that Could Scale (Easily) to Microservices (If They Need)
42mChopping the monolith