In a r/softwarearchitecture post, a lead architect argues to shatter a stable monolith into 47 microservices even though the system barely cranks out 2 requests per second. The video explores why this isn’t really about scaling – it’s more an org play, design fetish or maybe a misguided quest for developer autonomy.
The discussion covers real-world data (2 rps is trivial), how a monolith can actually scale fine, and the hidden costs of premature microservice sprawl: deployment headaches, cross-service latency, ops explosion. At the end of the day, value matters more than architectural fashion, so sometimes sticking with a well-oiled monolith is just the smarter move.
Watch on YouTube
Top comments (0)