47 Microservices for 2 RPS?! A lead architect wants to chop a perfectly stable monolith into 47 tiny services, even though the app barely sees two requests per second. A hot Reddit thread on r/softwarearchitecture hilariously pits developers—who warn about premature complexity—against architects chasing distributed-systems cred. Is this really about handling scale, or just flexing microservices muscles?
In theory, microservices bring isolated deploys, tech freedom and team autonomy. In practice, spinning up 47 end-to-end pipelines, choregraphy, monitoring and network calls for a handful of RPS feels like using a sledgehammer to crack a nut. Sometimes the “modern” shine of distributed systems just masks the fact that a lean monolith still rules.
Watch on YouTube
Top comments (0)