[radium3d]

Once you've had an outage on AWS, Cloudflare, Google Cloud, Akismet. What are you going to do? Host in house? None of them seem to be immune from some outage at some point. Get your refund and carry on. It's less work for the same outcome.

[CobrastanJorji]

Multi-cloud. It's fairly unlikely that AWS and Google Cloud are going to fail at the same time.

[radium3d]

Yeah, just double++ the cost to have a clone of all your systems. Worth it if you need to guarantee uptime. Although, it also doubles your exposure to potential data breaches as well.

[yeswecatan]

How do you handle replication lag for databases?

[Breza]

Why not host in house? If you have an application with stable resource needs, it can often be the cheaper and more stable option. At a certain scale, you can buy the servers, hire a sysadmin, and still spend less money than relying on AWS.

If you have an app that experiences 1000x demand spikes at unpredictable times then sure, go with the cloud. But there are a lot of companies that would be better off if they seriously considered their options before choosing the cloud for everything.

[grogers]

Certainly if you aren't even multi-region, then multi-cloud is a pipe dream

[bean469]

> What are you going to do? Host in house?

Yep. Although it's just anecdata, it's what we do where I work - haven't had a slightest issue in years.

[nxpnsv]

Cheaper, faster, in house people understands what’s going on. It should be a given for many services but somehow it’s not.

[erikpukinskis]

On premise? Or do you build servers in a data center? Or do you lease dedicated servers?

[cakeday]

> Host in house?

Yes, mostly.