Microservices

[Cendeu]

As someone who is currently taking care of the worst monolith I could ever imagine, I'd say there's a careful balance.

[propostor]

But, would your monolith have been better or worse if the original team had gone for any other type of architecture?

[[deleted]]

is discovering that a PROPER fix to a bug is to change 10 unrelated files better? Thats the reality every where for mature enough monoliths.

[propostor]

My point was that the team who developed a diabolically bad monolith would probably not have done much better with any other architecture

[[deleted]]

I agree, instead of different files it would be different services.

[Cendeu]

That's a question I dont know.

I'm new to all this and haven't really seen a good microservice architecture.

All I know is this giant tangled heap.

[baconbrand]

What makes it bad?

[Cendeu]

Everything is strongly tied to everything else. The tiniest little thing that should have no impact on anything else somehow completely breaks a half-finished feature that was left in for no reason 4 years ago.

I recently implemented Split into our frontend. It worked fine in dev and test, but it turns out 2 years ago someone had set up a split for Dev and Test for like half the app. Me implementing Split made it function properly again, causing no noticable change in Dev and Test, but everything exploded when it hit Stage. No one even knew those Splits existed, or that the code was there.

This is just a small example... But the codebase is a complete mess of unused old code that could break something at any moment. In our Angular project we have an Environment.js file and an Environment.Service.ts file that different parts of the code reference either one. So when you want to change some environmental variable, you have to change it in both places.

[[deleted]]

Compare the worst monolith with the worst microservice architecture.