BlogArchitecture
Architecture10 min read

The True Cost of Microservices: When Monoliths Win

Microservices add 50-100% infrastructure overhead. They're worth it only above a specific team size.

By Richard Ewing·

The Microservices Tax

Infrastructure overhead: 50-100% more than monolith (networking, orchestration, observability, service mesh). Operational complexity: 3-5x more deployment targets. Debugging: distributed tracing required (cost + complexity).

Microservices make economic sense when: team size >20 engineers, deployment Independence is critical, different services need different scaling, and team autonomy outweighs coordination cost.

Below 20 engineers: a well-structured monolith is almost always cheaper and faster.

Like this analysis?

Get the weekly engineering economics briefing — one email, every Monday.

Subscribe Free →

More in Architecture

Published Work

This article expands on ideas from my published work in CIO.com, Built In, Mind the Product, and HackerNoon. View published articles →

📊

Richard Ewing

The Product Economist — Quantifying engineering economics for technology leaders, PE firms, and boards.