[cellis]

Was nodding along until "...consolidating databases into a single underpowered behemoth...". Nothing worse than race conditions and stale data between multiple disparate datastores. I'd rather have one database and more ram for as long as possible, tyvm. Some of the latest nights I've had debugging were at companies with mission critical data spread across multiple databases. I know it's orthogonal to the point, but this one really didn't land with me.

[cnity]

This is basically the story of my career. It is very hard to argue for DB monoliths, and very common in a distributed microservice architecture for effectively doing joins across a network (with associated N+1 problems).

[ljm]

I guess the operative word is 'underpowered'.

My low-stakes conspiracy theory though is that cloud providers (and symbiotic entities in the ecosystem) have helped turn developers against monoliths in favour of self-serve microservice architectures and devops because there's a lot more money in it for them when people are spinning up dozens of hermetically sealed, over-provisioned services, each with their own DB, cache, load balancer, etc.

It's like corporate welfare, redistributing wealth from VCs to Bezos.

[unlogic]

The term "linear scaling" was invented by cloud companies to sell more cloud.