47 Microservices… for 2 Requests Per Second?!

A lead architect is dead set on carving a rock-solid monolith into 47 separate microservices—despite the app hardly breaking a sweat at just two requests per second. Cue a classic reddit showdown on r/softwarearchitecture where developers and architects duke it out over whether this is a case of genuine scaling needs or simply chasing trends (and org-chart glory).

At its core, the debate boils down to real versus perceived benefits: sure, microservices can help large teams own distinct domains, but do they justify the extra complexity when your traffic barely registers? From pondering the true cost of splitting the monolith to hunting for real business value, everyone’s asking if this move actually fixes anything—or just flexes architecture muscle.

Watch on YouTube