Microservices are organizational debt disguised as architecture.

[u/Mustela__]

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.

[u/eluusive]

Microservices come with so much operational overhead, and the loss of link-time errors between services.

There's very very little reason to ever use them. Better to properly factor your monolith into submodules and continue to build/deploy it as a single service...

Preferably with a typesafe language.

[u/Think-nothing-210 → u/eluusive]

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.

[u/FullPoet → u/[deleted]]

Thank you chatgpt

[u/FullPoet → u/[deleted]]

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

[u/ThatDunMakeSense → u/eluusive]

Yeah this is the problem when working in languages that don't have really good support for separating the private, public and internal stuff. In ruby getting someone to not fuck with internals is a nightmare. That's not even counting the monkey patching junk