"Today, a single user request might touch 15 services, 3 databases, 2 caches, and a message queue."

This right here is the fundamental problem because the way it's done is highly inefficient, complex and I believe only exists so cloud providers can sell their expensive offerings.

A monolith is fine 90% of the time.

▲

sgarland 4 hours ago | parent [-]

That, and everyone thinks they have to do things this way, so it’s a terrible cycle.

So many problems would be solved if service calls were IPC instead of network calls.

	▲	hoppp 2 hours ago \| parent [-]
		Ye, even the smallest projects nowadays are either serverless or run in kubernetes, they never even think about IPC. Modern deployment pipelines are very good at deploying services that are running in separate containers, and people hate custom shell scripts, even if they work great. If it's bespoke and not standardized its harder to maintain that's true, but its also great at reducing operational costs because infrastructure fees change with less reliance on external services . Its a cycle alright.