Regional B2B SaaS (pattern case) · 2017 · cost index 4/5
Mid-market CRUD shop splits into forty repos
3× infra spend; velocity flat for two years
What happened
Eighty engineers, one product, four customers who cared about SSO and invoices. A new VP imported Netflix slides. Kubernetes arrived. So did forty microservices, distributed tracing bills, and standups about contract versioning instead of features the sales team could demo.
Failure mode
Organizational cosplay without domain boundaries or SRE headcount. Shared libraries became semver nightmares. Local dev required half the cluster. The monolith had been boring; the mesh was fragile and expensive.
Lesson
Microservices buy independent deployability when teams and traffic justify the tax. If your bottleneck is product management, decomposing the codebase just makes you slower with better dashboards.
Sources
- Sam Newman — Monolith First
- Cindy Sridharan — distributed systems observability costs
- Industry pattern — mid-market microservice regret
Related tech
Architecture · 2012–now
Microservices Everywhere
Independent deployability as religion. Correct for some; ruinous cargo-cult for most.
$ 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.
Platform · 2013–now
Docker / Containers
Ship the environment with the code. The packaging unit of modern compute.
Architecture · 1970–now
Modular monolith
One deployable with clear boundaries. The unfashionable default that keeps shipping while microservices argue about ownership.
Architecture · 2015–now
gRPC
Binary RPC with contracts. Fast internal glue that should never face the public internet without a gateway.
Platform · 2011–now
Jenkins
Plugin palace CI that defined pipeline culture — and Groovy nightmares. Still running somewhere in your org.