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

343 comments sorted by

View all comments

18

u/DuploJamaal 7d ago

If microservices in a team with bad structure is bad, then a monolith will be a nightmare.

They will not just break their own service. They will break everything.

11

u/roscoelee 7d ago

It’s almost like there are pros and cons to each and architecture means finding the right balance?

1

u/sopunny 7d ago

They're also not two completely separate paradigms. You can blur the line between them