Live data from Hacker News

Migrating from AWS to Hetzner

digitalsociety.coop

471–480 of 643 posts

Re: Migrating from AWS to Hetzner

#471

I cannot overstate the performance improvement of deploying onto bare metal. We typically see a doubling of performance, as well as extremely predictable baseline performance. This is down to several things: - Latency - having your own local network, rather than sharing some larger datacenter network fabric, gives around of order of magnitude reduced latency - Caches – right-sizing a deployment for the underlying har…

We moved DemandSphere from AWS to Hetzner for many of the same reasons back in 2011 and never looked back. We can do things that competitors can’t because of it.

Can you please explain what are some of those things? Curious to know and learn.

Re: Migrating from AWS to Hetzner

#472
post #326

Saving $400/month covers about 3-5 hours of engineering time per month. In a year, call it 30-50 hours. Did this project take more than 30-50 person-hours? (The obvious argument about how it might pay off more in the future are dependent on the startup surviving long enough for that future to arrive.)

I feel like this is left out of the story too often - people tend to compare the most optimistic "self-hosted", usually just one or two servers at best, to a less than ideal cloud installation. My parent company (Healthcare) uses all on prem solutions, has 3 data centers and 10 sys admins just for the data centers. You still need DevOps too. I don't know how much it would cost to migrate their infra to AWS, but ~ $1.…

If your parent company sysadmins invest heavily into automation each sysadmin could be managing thousands of servers.

Also, 6000 CPU "cores" on the cloud is more like 3000 CPU cores. Which you can get in just 20-50 servers. This is in the range of something that could be taken care of as a part time job.

Re: Migrating from AWS to Hetzner

#473

Earlier quoted context omitted.

neo4j

What is the cost of running Neo4j on aws vs using aws Neptune? Related to disk I/o?

Tbh, I don't know. For us the switching cost alone would be pretty high. That said ongoing maintenance is pretty high as well.

Re: Migrating from AWS to Hetzner

#474

I love how few comments on this and similar posts give much context along with their advice. Are you hosting a church newsletter in your spare time or a resource intensive web app with millions of paying enterprise customers and a dedicated dev ops team in 3 continents? Any advice on price / performance / availability is meaningless unless you explain where you're coming from. The reason we see people overcomplicatin…

> a dedicated dev ops team in 3 continents

you don't need that in 99.9999% of cases.

Re: Migrating from AWS to Hetzner

#476
post #381

I cannot overstate the performance improvement of deploying onto bare metal. We typically see a doubling of performance, as well as extremely predictable baseline performance. This is down to several things: - Latency - having your own local network, rather than sharing some larger datacenter network fabric, gives around of order of magnitude reduced latency - Caches – right-sizing a deployment for the underlying har…

How do you deprogram your devs and ops people from the learned helplessness of cloud native ideology? I've found that it's almost impossible to even hire people who aren't terrified of the idea of self-hosting. This is deeply bizarre for someone who installed Linux from floppy disks in 1994, but most modern devs have fully swallowed the idea that cloud handles things for them that mere mortals cannot handle. This, in…

>I've found that it's almost impossible to even hire people who aren't terrified of the idea of self-hosting

Funny, I couldn't find a new job for a while because I had no cloud experience, finally and ironically I got hired at AWS. Every now and then these days I get headhunters unsure about my actual AWS experience because of my lack of certifications.

Re: Migrating from AWS to Hetzner

#477

Earlier quoted context omitted.

This is how the cloud companies keep you hooked on. I am not against them of course but the notion that no one can self host in production because "it is too complex" is something that we have been fed over the last 10-15 years. Deploying a production db on a dedicated server is not that hard. It is about the fact that people now think that unless they do cloud, they are amateurs. It is sad.

Doing stuff on-prem or in a data centre _is_ hard though. It's easy to look at a one-off deployment of a single server and remark on how much cheaper it is than RDS, and that's fine if that's all you need. But it completely skips past the reality of a real life resilient database server deployment: handling upgrades, disk failures, backups, hot standbys, encryption key management, keeping deployment scripts up to dat…

I guess that is the kicker right? "same level of guarantees".

Re: Migrating from AWS to Hetzner

#479
post #332
post #318

Earlier quoted context omitted.

You have a link to some proof that chat gpt is patching servers running databases with no down time or data loss?

I think the argument is that dev with some vibe coding can successfully setup servers that are good enough already for 10x less cost and 95% reliability

[deleted]

Re: Migrating from AWS to Hetzner

#480

This is pretty bad still, with colocation you can get the costs down to 1/100th with good deals at datacenters especially ones that are struggling to attract customers. Most of your bill is power so if you rack efficiency optimized servers you can have a lot of compute for very cheap. In terms of networking many offer no-headache solutions with some kind of transit blend. I recently had to switch away from hetzner du…

Cogent just offered me this colo deal: Full Rack = $100/month* with $500 install, Power (20A) = $350/month with $500 install, DIA (1Gbps) = $300/month Total = $750/month plus $1,000 Install on 12 month term

Where is this, if I may ask?
Post reply on HN