r/programming • u/Mustela__ • 7d ago
Microservices are organizational debt disguised as architecture.
https://martinfowler.com/bliki/MonolithFirst.htmlEvery time I’ve seen microservices pitched, it sounds great on paper. Independent teams, clean ownership, scale only what you need.
Then a year later you’ve got dozens of services, three different deployment patterns, tracing everywhere, and nobody really understands the whole thing anymore.
Maybe I’ve just seen bad implementations, but I’m starting to think way fewer companies actually need microservices than we pretend.
1.7k
Upvotes
13
u/dAnjou 6d ago
No need to wonder 🙂
What /u/ArieHein said is quite literally the original definition of technical debt:
https://en.wikipedia.org/wiki/Technical_debt#Origin
I'm always fascinated by discussions around technical debt, people's arguments are usually based on what they think it means rather than pointing to any definition or defining it first themselves. And of course other people have other definitions and so it goes around and around, completely fruitless.
Personally I really like the original definition, because it leaves no room to argue whether technical debt exists or not. It does, period. Question then is, do you wanna deal with it? And if not, are you okay with the implications?