Mark Richards at DDD Europe
summary
Argues that a single VM or server hits resource limits as traffic grows, showing with a glass and water demo that duplicating the VM just duplicates the overloaded state — monolith saturation persists because threads, memory and CPU remain constrained. Proposes breaking the application into separate services so each component scales independently, claims this yields sustainable growth, and demonstrates the change visually but provides no numeric throughput or latency measurements.
AI-written summary · about
related talks
38mIt's Simple…
39mWays out of a monolith
36mDo Proper Monoliths before You Do Microservices!
29mWhen Web Scale Doesn't Make Sense
45mThe Evolution From Monolith to Microservices to Serverless and Beyond
44mDemonolith the Monolith Think Again!
54mServices, Services, Everywhere!
23mMicroservices and containers