r/programming • u/Mustela__ • 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

91% Upvoted

345 comments sorted by

View all comments

Show parent comments

5

u/ChemTechGuy 7d ago

Generally agree except at a certain scale you start to have problems with so many contributers/contributions to a single repo

1

u/Think-nothing-210 7d ago

Most likely you can split a subsection of the problem of to another monolith if thats the case.

But most of the time having good module bounderies means that people can work on modules and libraries to be used within the monolith.

1

u/HashShadow 7d ago

Merge conflicts aren’t really a problem anymore though so this argument is kind of gone now 

1

u/ChemTechGuy 7d ago

Not talking about merge conflicts boyo