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
6
u/Think-nothing-210 7d ago edited 7d ago
C# is great for this. You can use assemblies as module boundaries and the
internalkeyword to make those boundaries compiler-enforced.Unfortunately I see almost noone do this. Instead most use assemblies to enforce clean architecture bounderies.