47 Microservices… for 2 RPS?
A lead architect is pushing to slice a rock-solid monolith into 47 tiny microservices, even though this app barely hits 2 requests per second. The Reddit thread on r/softwarearchitecture perfectly captures the classic developers-vs-architects tug-of-war: Is splitting really about handling huge loads, or is something else driving the urge?
At its core, the debate isn’t about scaling—2 RPS won’t break your monolith—but about team ownership, flexibility, and that looming “distributed systems tax.” Sure, microservices can boost autonomy and let squads ship independently, but 47 moving parts also mean 47 more things to monitor, debug, and stitch together. Is the complexity worth it for a traffic level you could handle on a single server?
Watch on YouTube
Top comments (0)