This is why microservices can make sense for large companies with many, separate, and isolated teams. And why it just about never makes any sense for small companies where teams can grasp the entire application.https://twitter.com/CodeWisdom/status/1177925174533984257 …
-
Right. Microservices are a technical debt that you accept because the gained organizational simplicity is worth it in very large companies.
In that case: monoliths are a technical debt that you accept temporarily until your organization is sufficiently large to necessitate microservices. Or, microservices are a technical debt you accept in small organizations in order to prevent painful refactoring.
-
-
I think that's the paddled narrative that is counterfactual. The people who benefit from this narrative is everyone who works on a billable hour basis, which happens to be the loudest part of the developer community
-
Ah, I may have misinterpreted your tweet. I took it as “microservices are an inevitable/necessary technical debt for large companies” - though maybe you’re saying it’s not necessary? My point was that if it *is* necessary, then a monolith is, by definition, a technical debt.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.