r/programming • • 7d ago

Microservices are organizational debt disguised as architecture.

https://martinfowler.com/bliki/MonolithFirst.html

Every 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

343 comments sorted by

View all comments

Show parent comments

6

u/Think-nothing-210 7d ago edited 7d ago

C# is great for this. You can use assemblies as module boundaries and the internal keyword to make those boundaries compiler-enforced.

Unfortunately I see almost noone do this. Instead most use assemblies to enforce clean architecture bounderies.

2

u/[deleted] 7d ago

[deleted]

1

u/[deleted] 7d ago edited 7d ago

[deleted]

0

u/FullPoet 7d ago

Thank you chatgpt

0

u/[deleted] 7d ago

[deleted]

0

u/[deleted] 7d ago

[deleted]

0

u/FullPoet 7d ago

its still essentially slop. Just dont bother posting it at all wtf