A lead architect is itching to carve a perfectly stable monolith into 47 microservices—even though the app barely hits two requests per second—sparking a lively r/softwarearchitecture debate. Developers are calling it overkill, wondering if this push is really about scaling or just about chasing microservices for microservices’ sake.
The thread dives into organizational needs vs. technical reality, weighing monolith-scaling tricks, team structures, operational overhead, and real business value. It really makes you question: at what point does breaking stuff apart stop making sense?
Watch on YouTube
Top comments (0)