47 Microservices for 2 RPS?! A lead architect wants to carve a perfectly stable monolith into 47 microservices, even though the app only handles about two requests per second. This perfectly captures the age-old tussle between developers and architects: is this really about scaling, or just scratching an architectural itch?
Critics point out the massive overhead of service sprawl—extra ops, testing and team coordination—when you’ve got almost zero traffic. Supporters argue microservices bring clearer ownership, independent deployments and faster feature delivery. The real takeaway? Don’t chase microservices as a trophy; wait until there’s concrete value and ROI before chopping up your monolith.
Watch on YouTube
Top comments (0)