[p1necone]

Yeah the delta in cost/CPU/memory/storage between self hosting on second hand stuff and paying cloud services is insane. It's a no brainer if your use case needs beefier hardware than the typical $5/month VPS host and you don't have enterprise level liability/uptime expectations.

With stuff like proxmox you get a pretty similar level of ease of use to managed VM services too.

[Karrot_Kream]

I generally find these discussions unproductive on HN because of how binary they become, but definitely once you go off the beaten path it seems a lot cheaper (sans power though) to run your own infra. I've been thinking of doing some data ETL for something that generates 1 GB / day and has retention for 30 days and it's much cheaper to host a Postgres myself at that scale than run it in the cloud. I could store in something like S3, but then I need to deal with querying S3. I'd like to combine some of this with cloud infra but I suspect cloud bandwidth costs would kill me. Colo-ing 2-3 servers is probably the best bet here.

[calvinmorrison]

I was an ops engineer at Fastmail. We ran our own hardware. A mix of Debian on one stack and SmartOS (Illumos from Joyent) and there were plenty of physical problems and costs. Now putting petabytes of data with replication and syncing and all that would have been a cluster F on the cloud, we missed out on a lot of the awesome newer deployment other tooling because we had written our own. Before I left we swapped out a good chunk of these snowflake software but it was impressive actually how well it worked. Good multi data center multi master mysql support in 2008? Killer feature. Maintaining that in 2020? Horrible.

Also there were plenty of upstream routing issues where solving that became a headache. The #1 thing we wanted was uptime and the #1 outage was our upstream providers having trouble routing to other upstream providers.

The number one reason and tradeoff for cloud is uptime and availability and the cost of not having it

[Karrot_Kream]

> The number one reason and tradeoff for cloud is uptime and availability and the cost of not having it

100%. I ran API networking teams at a Big Tech and I know the difference. My workload here is at a hobbyist+ grade, no controls, no compliance, best effort SLA. I don't want to ignore the reality that to get enterprise grade uptime and availability, it's really hard to do this on prem.

[TacticalCoder]

> The number one reason and tradeoff for cloud is uptime and availability and the cost of not having it

Uptime? There have been quite a few catastrophic cloud failures. And some lasted hours.

Five nine is something like 5 minutes of downtime a year. The clouds aren't anywhere near that.

[Unroasted6154]

If you use it correctly, with multiple availability zones and even multi regions you can reach very high reliability. They surely don't offer five 9s for a single zone. I am not aware of many multi regions outages. And they are also getting better over time, spending a lot more engineering hours on reliability that most companies. And if they fail to deliver on SLA they might give you money (depending on your contract I guess).

[throwaway2037]

Do you really think on-prem has more uptime than commercial cloud? For non-tech companies, no even close. Commercial cloud is adding nines to uptime and saving money by removing in-house IT admin staff.

[calvinmorrison]

the biggest miscalculation is really on expected uptime. People say they need 5 nines, yet take their car in for service twice a year for a tire rotation and oil change. How much uptime is _really_ required?

[ilyt]

It's insane between actually renting servers, or even classical "bare" VPS providers and cloud too.