Microservices Overuse Debate
The cluster centers on criticisms of microservices architecture being adopted prematurely or excessively, often by managers without real need, versus appropriate use cases like large teams, with discussions on alternatives like monoliths.
Activity Over Time
Top Contributors
Keywords
Sample Comments
The problem is when a manager that "used to code" reads an article and decides that micro services are the answer to everything. Then it spreads around the company like a disease, until you find yourself repeatedly having to explain that "micro services can be useful in some scenarios, and we should keep an open mind, but for our particular use case it would just make things more difficult without adding any benefit."
That sounds more like a criticism of microservices, which can definitely be overdone.
Wait, is that why we all have microservices now?
You mean the flawed microservices architecture where everything is so complicated it's almost not worth doing.
What if microservices are actually an anti-pattern?
The comment was arguing the use of microservices is far more common than the need for microservices. And based on your description it sounds like you guys were one of the few that had a need for microservices.
not everyone is developing microservices.
Sounds like what you're really angry at here is a case of micro-services taken to the extreme.
This is completely wrong, everyone knows you should rewrite everything in microservices immediately :-D
Nailed it. Micro-services are not necessarily always the answer (good devops is), but they encourage doing the "right thing".