Heh

Once you have a service that has users and costs actual money, while you don’t need to make it a spaghetti of 100 software products, you need a bit of redundancy at each layer — backend, frontend, databases, background jobs — so that you don’t end up in a catastrophic failure mode each time some piece of software decides to barf.

▲

blkhawk 2 days ago | parent [-]

uh, maybe you only have the issue that you need redundancies because you have so many pieces of software that can barf?

I mean it will happen regardless just from the side effects of complexity. With a simpler system you can at least save on maintenance and overhead.

	▲	WesolyKubeczek 2 days ago \| parent [-]
		Yes, but if your web server goes down for whatever reason, you’d rather have some more for your load balancer to round robin. Things like physical host dying are not exactly unheard of. Same with DB, once you take money, you want that replication and quick failover and offsite backup.