Architecture · 2012–now · Cloud Scale

Microservices Everywhere

Independent deployability as religion. Correct for some; ruinous cargo-cult for most.

Microservices failed as a default because network boundaries multiply failure modes faster than team autonomy. Netflix needed it; your CRUD shop needed a modular monolith and sleep. The fad cost was paying senior distributed systems salaries to ship slower.

Cost of the fad

Teams split 4-person products into 40 services, then hired SREs to babysit the mesh. Many later consolidated — after years of distributed tracing invoices and on-call trauma. See case studies on premature microservices and big-bang cutovers for named failure modes.

Case studies

Patterns

Context

Split everything, then pay for the glue

Hyperscale patterns escaped the companies that needed them. Containers unified packaging; Kubernetes became the cloud OS; microservices and NoSQL were sold as defaults. Mobile-first stuck because screens changed. Cargo-cult distributed systems stuck around as invoices. The durable move was packaging and ops maturity — not rewriting every app into a mesh.

Compare with

Related

© 2026 Fadstack · Shane Code

Opinionated history · not a ranking