I always appreciate savings posts, but is $14k USD annual really make or break for a Turkish business? I would not know.
Migrating from DigitalOcean to Hetzner
21–30 of 454 posts
Re: Migrating from DigitalOcean to Hetzner
#22> Cloud providers are expensive for steady-state workloads. Asking the obvious question: why not your own server in a colo?
Then, say if the motherboard gives up, you have to do quite a bit of work to get it replaced, you might be down for hours or maybe days.
For a single server I don't think it makes sense. For 8 servers, maybe. Depends on the opportunity cost.
Re: Migrating from DigitalOcean to Hetzner
#23I saved about $1200 a year by moving from AWS to Hetzner. Can’t recommend it enough. AWS has kind of become a scam.
It's worse than Oracle and they don't even use lawyery contracts.
The technology itself is the tendrils.
Re: Migrating from DigitalOcean to Hetzner
#24We need more competition across the board. These savings are insane and DO should be sweating, right?
One of the new risks is if anything critical happens with the hardware, network, switch etc. then everything is down, until someone at Hetzner go fixes it.
With a virtual server it’ll just get started on a different server straight away. Usually hypervisors also has 2 or more network connections etc.
And hopefully they also got some backup setup.
It’s still a huge amount of of savings and I’d probably do the same of I were in their shoes, but there is tradeoffs when going from virtual- to dedicated hardware.
Re: Migrating from DigitalOcean to Hetzner
#25> Cloud providers are expensive for steady-state workloads. Asking the obvious question: why not your own server in a colo?
Re: Migrating from DigitalOcean to Hetzner
#26What are you doing for DB backups? Do you have a replica/standby? Or is it just hourly or something like that? Because with a single-server setup like this, I'd imagine that hardware (e.g. SSD) failure brings down your app, and in the case of SSD failure, you then have hours or days downtime while you set everything up again.
Once the first SSD fails after some years, and your monitoring catches that, you can either migrate to a new box, find another intermediate solution/replica, or let them hotswap it while the other drive takes on.
Of course though, going to physical servers loses redundency of the cloud, but that's something you need to price in when looking at the savings and deciding your risk model.
And yes, running this without also at least daily snapshotting/backup to remote storage is insane - that applies to cloud aswell, albeit easier to setup there.
Re: Migrating from DigitalOcean to Hetzner
#27I always appreciate savings posts, but is $14k USD annual really make or break for a Turkish business? I would not know.
That's not the point. You should be asking why DO is so much more expensive. Not everyone likes wasting money.
Re: Migrating from DigitalOcean to Hetzner
#28What are you doing for DB backups? Do you have a replica/standby? Or is it just hourly or something like that? Because with a single-server setup like this, I'd imagine that hardware (e.g. SSD) failure brings down your app, and in the case of SSD failure, you then have hours or days downtime while you set everything up again.
Yeah. This blog post reads like it was written by someone who didn't think things through and just focused on hyper-agressive cost-cutting.
I bet their DigitalOcean vm did live migrations and supported snapshots.
You can get that at Hetzner but only in their cloud product.
You absolutely will not get that in Hetzner bare-metal. If your HD or other component dies, it dies. Hetzner will replace the HD, but its up to you to restore from scratch. Hetzner are very clear about this in multiple places.
Re: Migrating from DigitalOcean to Hetzner
#29> Cloud providers are expensive for steady-state workloads. Asking the obvious question: why not your own server in a colo?
Have you seen what the LLM crowd have done to server prices ?
Re: Migrating from DigitalOcean to Hetzner
#30I use OVH btw.