A lead architect is itching to slice up a perfectly stable monolith into 47 tiny microservices—even though the app barely handles 2 requests per second. A hot Reddit thread on r/softwarearchitecture lays out the classic developer vs. architect tussle: is this microservice mania really about handling massive scale, or is it more about chasing buzzwords and flexing tech cred?
The video (and linked discussion) walks through different angles: real-world performance needs, organizational size, the art of scaling a monolith, and where actual business value fits in. Ultimately, it asks: when does breaking things apart actually help, and when is it just extra complexity?
Watch on YouTube
Top comments (0)