Successful microservice systems almost always began as a monolith that grew too big, and systems built as microservices from scratch end up in serious trouble.

Added to korrents 3 Jun 2015 · How quotes work · Something wrong? Tell us

Related korrents

Our reading — they may agree, disagree or merely touch the same thing. Closest first: a shared subject counts for most, then how near the wording is.

• Build a new application as a monolith first, even when you are confident it will eventually need microservices. MFMartin Fowler3 Jun 2015similar wording
• Service boundaries cannot be got right at the start, and moving functionality between services is far harder than moving it inside a monolith. MFMartin Fowler3 Jun 2015similar wording
• Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive. TPThuan Pham1 Apr 2026similar wording
• Kubernetes won because Docker had already won: it inherited the one container runtime the whole industry had agreed on, instead of shipping another. KHKelsey Hightower3 Jun 2026similar wording
• Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible. DHDavid Heinemeier Hansson26 Aug 2026similar wording

See this on the map →