47 Microservices for 2 RPS?! A lead architect wants to shatter a perfectly fine monolith into 47 tiny services—despite the app barely seeing two requests per second—sparking a classic devs-vs-architects smackdown. Is it really about scaling, or more about organizational politics, career clout, and the mythical “bus factor”?
The debate hits on real vs. perceived needs: your two-RPS app doesn’t demand microservices when you can scale a monolith with caching, sharding, and queues. Microservices bring versioning headaches, extra ops overhead, and team coordination pains—so choose the simplest architecture that delivers actual business value, not just tech buzz.
Watch on YouTube
Top comments (0)