47 Microservices… for 2 Requests Per Second?!
A lead architect wants to chop a chill, stable monolith into 47 microservices—even though the app barely sees 2 requests per second. This Reddit thread on r/softwarearchitecture highlights the tug-of-war between architects hunting tech elegance and devs worrying about overkill, ops complexity, and whether you really need so many moving parts just to keep the lights on.
It’s not just about raw performance. The real debate digs into organizational scale (team boundaries, ownership) versus system scale (throughput, latency). Sometimes the smartest move isn’t more services, but making the monolith work harder and smarter.
Watch on YouTube
Top comments (0)