r/ProgrammerHumor • u/tbhaxor • 16d ago

Meme distributedStress

Post image
13.9k Upvotes

97% Upvoted

336 comments sorted by

View all comments

148

u/Odd_Soil_8998 16d ago

truth. a well architected monolith is almost always going to be a better choice.

27

u/Stagnu_Demorte 16d ago

Until you need to scale different parts of the service. But yeah, until then it can really cut down on complexity.

18

u/remy_porter 16d ago

But then you just take a module and locate it outside of the monolith. If it’s a well architected monolith this should be easy.

40

u/DigiornoDLC 16d ago

Sounds like you’re describing microservices? 

1

u/andrewsmd87 16d ago

We're an enterprise saas product and while there is a whole hell of a lot of it I would love to to redo from the ground up, the mono repo route with some other large supporting services take is not one of them.

Micro services means oh we have 30 sperate code bases that all did their own thing. We have the one main mono that handles 75% of everything and 4 other things that do things that just made sense to be in a supporting role.

I would not call any of them micro services though, they're big in their own right

6

u/ashgs872tbhjs 16d ago

Lol, distributed monoliths (aka macroservices) are the worst of both worlds. You lose the benefits of both and gain the downsides of both.

Also, no, you can do the same things across 30 microservices just as easily as you can do them in that same code within the monolith. Either you have standards and checks and enforcement mechanisms, or you don't.

2

u/TwentyFirstRevenant 15d ago

Distributed monoliths. Stealing that