TL;DR
A lead architect insists on carving a perfectly stable monolith into 47 tiny microservices—despite the app barely seeing 2 requests per second. The reddit thread unpacks the classic tug-of-war: are we really doing this for scale, or is it more about architecture fashion, team structure, and perceived “modern” best practices?
Developers argue a lean monolith still handles growth just fine, while architects talk organizational alignment, independent deployments, and future-proofing. At the end of the day, the real question isn’t raw RPS—it’s finding the balance between complexity and value.
Watch on YouTube
Top comments (0)