Architecture · 2017–2024 · Cloud Scale
Service mesh everywhere
Sidecar proxies for every microservice. Netflix problems with startup headcount.
Why Service mesh everywhere became a costly fad
Service mesh everywhere failed because sidecars multiply latency and operational surface faster than they solve auth between services you should have merged. mTLS and retries belong in libraries or platforms, not mandatory tax on every pod. The mesh stuck at true multi-team scale; the fad stuck in post-mortems.
Cost of the fad
What Service mesh everywhere cost
Istio sidecars on three-service startups burned SRE headcount on mTLS ceremonies nobody could debug. Many teams ripped mesh out before the observability dashboard paid rent.
Case studies
Patterns
Compare with
Related
Architecture · 2012–2023
Microservices Everywhere
Independent deployability as religion. Correct for some; ruinous cargo-cult for most. Consolidation and monolith return are the 2020s epilogue.
$ 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.
Platform · 2014–now
Kubernetes
Container orchestration that became the cloud's OS. Overkill for many; unavoidable for many others.
Architecture · 2015–now
gRPC
Binary RPC with contracts. Fast internal glue that should never face the public internet without a gateway.