Summary
A lead architect is pushing to slice a perfectly stable monolith into 47 microservices—despite the app only handling about 2 requests per second. A lively Reddit thread on r/softwarearchitecture uses this extreme example to highlight the eternal tug-of-war between developers and architects over when (and why) to break up a monolith.
The real crux isn’t raw scaling—it’s about team boundaries, deployment complexity, and the perceived “value” microservices bring. Sometimes the simplest setup wins, especially when your traffic barely registers on the radar.
Watch on YouTube
Top comments (0)