47 Microservices… for 2 Requests Per Second?!
Imagine chopping up a perfectly fine monolith that only handles 2 requests per second into 47 microservices. That’s exactly the controversial proposal a lead architect floated on r/softwarearchitecture, kicking off a lively debate about whether this split is truly about scaling or just an itch for the latest architectural trend.
In this video, CodeOpinion unpacks why “scaling” often becomes the default justification, explores how organizational dynamics and team structure drive these decisions, and offers down-to-earth advice on weighing the real value of microservices versus the extra complexity they introduce.
Watch on YouTube
Top comments (0)