Let's say you're building a with a team of 2 people.
You've decided to run 3 services on , with 4 environments (dev, staging, QA, prod, etc).
Your local development uses , and you've built 3 abstraction layers (repositories, services, DTOs, etc).
Your complexity tax
Based on your choices, you're spending approximately 8.5 hours/week on complexity overhead.
That's 442 hours per year, or 55 workdays not spent on your actual product.
Where the time goes
The simpler alternative
If you ran 1 service on a PaaS with 2 environments (dev + prod), using native tooling and 0 abstraction layers:
You'd recover 390 hours/year — that's ~10 weeks of full-time work back to building product.
When complexity is worth it