I see, I’m definitely biased towards micro services after years of dealing with horribly made monoliths but I see what you mean.

At the end of the day I think both approaches have pros and cons.

Micro services are a lot easier to scale out since they behave independently from each other, you can have different levels of replication and concurrency based on the traffic that each part of your system receives.

Something that I think is pretty huge is that, done right, you end up with a bunch of smaller databases, meaning you can save a lot of money by having different levels of security and replication depending on how sensitive the data is.

This last part also helps with data residency issues, which is becoming a pretty big deal for the EU.

I somewhat agree but I find that the added complexity is segmented, you shouldn’t need to care about anything but the contracts themselves when working within a micro service.

That means less code to take into account, less spaghetti and an easier time with local testing.

Micro services also have a ton of advantages at the infrastructure level.

Exactly! Monoliths can work in theory but, in practice, end up becoming bloated messes since it’s just easier to do so.

It’s really not, you’ll be thankful you have it once the system grows too big.

Things just got darker over here, my screen would be completely black if it were still usable.