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

401–410 of 643 posts

Re: Migrating from AWS to Hetzner

#401

Post by GordonS »

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…

I've ran into the IP deny list problem too, but for Windows VMs - you spin them up, only to realise that you can't get Windows Updates, can't reach the Powershell gallery etc.

And just deleting it and starting again is just going to give you the exact same IP again!

I ended up having to buy a dozen or so IPs until I found one that wasn't blocked, and then I could delete all the blocked ones.

Re: Migrating from AWS to Hetzner

#402

Post by slig »

baobun wrote: post #134
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/

Also, Pigsty [1]. Feels too bloated for my taste, but I'd love to hear any experience from fellow HNers.

[1] https://pigsty.io/

Re: Migrating from AWS to Hetzner

#403

Post by fwip »

grim_io wrote: post #347
Arch-TK wrote: post #315

Earlier quoted context omitted.

What is more likely to fail? The hardware managed by Hetzner or your product? I'm not saying that you won't experience hardware failures, I am just saying that you also need to remember that if you want your product to keep working over the weekend then you must have someone ready to fix it over the weekend.

Cloud providers and even cloudflare go down regularly. Relax.

Sure - but when AWS goes down, Amazon fixes it, even on the weekends. If you self-host, you need to pay a person to be on call to fix it.

Re: Migrating from AWS to Hetzner

#404

Post by 999900000999 »

Long long ago, at the start of my career I was at a great company. We were using a Postgres DB version not supported by RDS. So I had to manually set up postgres over and over again on EC2 instances. This was before Docker was reliable/standard.

I wasted hours on this, and the moment RDS starts to support the postgres version we need it everything was much easier.

I still remember staying up till 3:00 a.m. installing postgres, repeatedly.

While this article is nice, they only save a few hundred dollars a month. If a single engineer has to spend even an hour a month maintaining this, it's probably going to be a wash.

And that's assuming everything goes right, the moment something goes wrong you can easily wipe out a year saving in a single day ( if not an hour depending on your use case).

This is probably best for situations where your time just isn't worth a whole lot. For example let's say you have a hobbyist project, and for some reason you need a very large capacity server.

This can easily cost hundreds of dollars a month on AWS, and since it's coming out of your own pocket it might be worth it to spend that extra time on bare metal.

But, at a certain point you're going to think how much is my time really worth. For example, and forgive me for mixing up terms and situations, ghost blog is about $10 a month via their hosted solution. You can probably run multiple ghost blogs on a single Hetzner instance.

But, and maybe it was just my luck, eventually it's just going to stop working. Do you feel like spending two or three hours fixing something over just spending the $20 a month to host your two blogs ?

Re: Migrating from AWS to Hetzner

#405

Post by wredcoll »

Arch-TK wrote: post #315
kitd wrote: post #253

Earlier quoted context omitted.

People are usually the biggest cost in any organisation. If you can run all your systems without the sysadmins & netadmins required to keep it all upright (especially at expensive times like weekends or run up to Black Friday/Xmas), you can save yourself a lot more than the extra it'll cost to get a cloud provider to do it all for you.

What is more likely to fail? The hardware managed by Hetzner or your product? I'm not saying that you won't experience hardware failures, I am just saying that you also need to remember that if you want your product to keep working over the weekend then you must have someone ready to fix it over the weekend.

I mean, yes, but also I get "3 nines" uptime by running a website on a box connected to my isp in my house. (it would easily be 4 or 5 nines if I also had a stable power grid...)

There's a lot, a lot of websites where downtime just... doesn't matter. Yes it adds up eventually but if you go to twitter and its down again you just come back later.

Re: Migrating from AWS to Hetzner

#407

Post by gizzlon »

ksajadi wrote: post #107
normie3000 wrote: post #92

Earlier quoted context omitted.

This is one key draw to Big Cloud and especially PaaS and managed SQL for me (and dev teams I advise). Not having an ops background I am nervous about: * database backup+restore * applying security patches on time (at OS and runtime levels) * other security issues like making sure access to prod machines is restricted correctly, access is logged, ports are locked down, abnormal access patterns are detected * DoS and…

I can attest to that. At Cloud 66 a lot of customers tell us that while the PaaS experience on Hetzner is great, they benefit from our managed DBs the most.

What's the "the PaaS experience on Hetzner" ? Link?

Re: Migrating from AWS to Hetzner

#408

Post by lkrubner »

They went from $559.36 to $132 a month on Hetzner, and they seem happy about the performance. This matches my own experience as well, I have been stunned regarding Hetzner and how cheap it can be.

Re: Migrating from AWS to Hetzner

#410

Post by wredcoll »

Esophagus4 wrote: post #197
Thicken2320 wrote: post #164

Earlier quoted context omitted.

Using the S3 API is like chopping onions, the more you do it, the faster you start crying.

Haha! My only “yes, but…” is that this: > 50k API calls per second (on S3 that is $20-$250 _per second_ on API calls!). kind of smells like abuse of S3. Without knowing the use case, maybe a different AWS service is a better answer? Not advocating for AWS, just saying that maybe this is the wrong comparison. Though I do want to learn about Hetzner.

You're (probably) not wrong about the abuse thing, but it sure is nice to just not care about that when you have fixed hardware. I find trying to guess which of the 200 aws services is the cheapest kinda stressful.
Post reply on HN