Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating from AWS to Hetzner

digitalsociety.coop

Post reply on HN
Print view View original

131–140 of 643 posts

Re: Migrating from AWS to Hetzner

#131

Post by amelius »

sergioisidoro wrote: post #108
roflmaostc wrote: post #95

Earlier quoted context omitted.

Sorry to hear that. But if you do not pay and you do not check your e-mails, it's basically your fault. Who is using SMS these days even?

Yes, absolutely my fault. But these problems happen. Credit cards expire, people change companies or go on leaves, off boarding processes are not always perfect, spam filters exist. Add to that the declining experience of email with so much marketing and trash landing in the inbox (and sometimes Gmail categorizing important emails as "Updates") That's why grace periods for these situations are important. Who uses SMS…

How long after shutting you down did they delete your data?

That period should definitely be longer than a few days.

Re: Migrating from AWS to Hetzner

#132

Post by netdevphoenix »

croes wrote: post #23
breadislove wrote: post #19

Hetzner is really great until you try to scale with them. We started building our service on top of Hetzner and had couple 100s of VMs running and during peak time we had to scale them to over 1000 VMs. And here couple of problems started, you get pretty often IPs which are black listed, so if you try to connect to services hosted by Google, AWS like S3 etc. you can't reach them. Also at one point there were no VMs a…

Blacklisted by whom?

The big cloud providers I am assuming

Re: Migrating from AWS to Hetzner

#133

Post by kees99 »

jwr wrote: post #76
lisperforlife wrote: post #11

I think you can get much farther with dedicated servers. I run a couple of nodes on Hetzner. The performance you get from a dedicated machine even if it is a 3 year old machine that you can get on server auction is absolutely bonkers and cannot be compared to VMs. The thing is that most of the server hardware is focused towards high core count, low clock speed processors that optimize for I/O rather than compute. It…

I actually benchmarked this and wrote an article several years back, still very much applicable: https://jan.rychter.com/enblog/cloud-server-cpu-performance-...

Did you "preheat" during those tests? It is very common for cloud instances to have "burstable" vCPUs. That is - after boot (or long idle), you get decent performance for first few minutes, then performance gradually tanks to a mere fraction of the initial burst.

Re: Migrating from AWS to Hetzner

#134

Post by baobun »

pwmtr wrote: post #47

We’ve been seeing the same trend. Lots of teams moving to Hetzner for the price/performance, but then realizing they have to rebuild all the Postgres ops pieces (backups, failover, monitoring, etc.). We ended up building a managed Postgres that runs directly on Hetzner. Same setup, but with HA, backups, and PITR handled for you. It’s open-source, runs close to the metal, and avoids the egress/I/O gotchas you get on A…

In the adjacent category of self-managed omakase postgres: https://www.elephant-shed.io/

Re: Migrating from AWS to Hetzner

#135

Post by tom1337 »

kachapopopow wrote: post #81

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…

But when you are Colocating you have higher upfront costs as you need to acquire hardware and also need to have somebody nearby the datacenter for hardware swaps in case of a failure, no?

Re: Migrating from AWS to Hetzner

#136

Post by debian3 »

lossolo wrote: post #80
cisophrene wrote: post #33

Dedicated servers on a host like Hetzer and OVH surely beats any virtualization based cloud offering on price and performance. The tradeoff is availability. It's a great choice for entities that are optimizing on cost, but not a great choice if your business cannot tolerate downtime. A good example is a the big lichess outage from last year [1]. Lichess is a non-profit, and also must serve a huge user base. Given the…

> The tradeoff is availability. This is a myth, created so cloud providers can sell more, and so those who overpay can feel better. I've been using dedicated servers since 2005, so for 20 years across different providers. I have machines at these providers with 1000-1300 days of uptime.

Same here, been running dedicated servers with OVH since 2009, if anything bare metal server are more stable than before. I just replaced a set of servers that was from 2018, I didn’t have any hardware problems during their 8 years of working under significant load. During that time I had 2 or 3 power outages, a few more network outages. Usually problems come in a cluster. I had a few years that I had nothing to report, 100% uptime. Dedicated are nice, but I guess it scares people. Hetzner use lower hardware quality than OVH on some of their offerings, so your experience may vary. One of the most important thing is to check that your server use datacenter SSD/HDD with ECC ram, it saves you a lot of problems.

Re: Migrating from AWS to Hetzner

#138

Post by baobun »

e12e wrote: post #85

Very interesting and detailed article! I'd love to hear more about how you use terraform and helm together. Currently our major friction in ops is using tofu (terraform) to manage K8s resources. Avoiding yaml is great - but both terraform and K8s maintaining state makes the deployment of helm from terraform feel fragile; and vice-versa depending on helm directly in a mostly terraform setup also feels fragile.

Not OP but I've lived through this too and my conclusion from that is that if you're doing tofu/terraform you're better off not introducing helm at all. Just tf the k8s.

Re: Migrating from AWS to Hetzner

#139

Post by IshKebab »

Hikikomori wrote: post #45
croes wrote: post #23

Earlier quoted context omitted.

Blacklisted by whom?

AWS at least maintains IP lists of bots, active exploiters, ddos attackers, etc, that you can use to filter/rate limit traffic in WAF. Not so much AWS that blocks you but customers that decide to use these lists.

Nice IPs you've got there Hetzner, shame if...

Re: Migrating from AWS to Hetzner

#140

Post by JCM9 »

As competition heats up, the relative “enshitifcation” of AWS is real.

There just isn’t a compelling story to go “all in on AWS” anymore. For anything beyond raw storage and compute the experience elsewhere is consistently better, faster, cheaper.

It seems AWS leadership got caught up trying to have an answer for every possible computing use case and broadly ended up with a bloated mess of expensive below-bar products. The recent panicked flood of meh AI slop products as AWS tries to make up for its big miss on AI is one such example.

Would like to see AWS just focus on doing core infrastructure and doing it well. Others are simply better at everything that then layers on top of that.

Post reply on HN