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

Migrating from DigitalOcean to Hetzner

isayeter.com

Post reply on HN
Print view View original

141–150 of 454 posts

Re: Migrating from DigitalOcean to Hetzner

#141

Post by MikeNotThePope »

rdevilla wrote: post #127
sph wrote: post #101

Earlier quoted context omitted.

I have just seen with my own eyes Claude astroturfing on a gamedev subreddit from a botting account that was picked up by Google so I could see a few of their other comments. This account's operation was going on development subs complaining about how good Claude's latest model is and how awful it is being afraid of losing one's job to AI. I know your comment is tongue-in-cheek and the poster here is kinda known, but…

The whole internet is like this now, and it's only just getting started. Makes me sick tbh, and I am still questioning if this is the kind of industry I want to work in.

For those who remember Digg, the recently relaunched a new version and shut it down almost immediately. They were getting hammered with AI bots when it was realized the Digg apparently still has good SEO. The explain it right on homepage.

https://digg.com/

Re: Migrating from DigitalOcean to Hetzner

#142

Post by brianwawok »

adamcharnock wrote: post #62

This is something we've[0] done a number of times for customers coming from various cloud providers. In our case we move customers onto a multi-server (sometimes multi-AZ) deployment in Hetzner, using Kubernetes to distribute workloads across servers and provide HA. Kubernetes is likely a lot for a single node deployment such as the OP, but it makes a lot more sense as soon as multiple nodes are involved. For backups…

Moving around k8s deployments is really nice. Very little vendor lockin compared to many of the cloud things you can buy.

My entire stack is.. k8s, hosted Postgres, s3 type storage. I can always host my own Postgres. So really down to k8s and s3. I think hetzner has some kind of s3 storage but haven’t looked into, and I assume moving in 100 TB is a process….

Re: Migrating from DigitalOcean to Hetzner

#143

Post by daneel_w »

traceroute66 wrote: post #28
Doohickey-d wrote: post #13

What 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.

> Because with a single-server setup like this, I'd imagine that hardware ... 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 o…

Surely you must've noticed that pretty much all of their bare metal offerings ("dedicated" and the stuff on "auction") have multiple disks, allowing for various RAID configurations?

Re: Migrating from DigitalOcean to Hetzner

#144

Post by desireco42 »

I think Digital Ocean is not something where I would worry about costs. I would prefer server like Hetzner but I don't think DO is service where the costs are such that we need to do movement.

Plus, this is not what DHH was doing, he was not saving few bucks, but unlocking potential for his company to thrive.

Re: Migrating from DigitalOcean to Hetzner

#145

Post by readyforbrunch »

pmdr wrote: post #119

I started with DO in 2013 when they offered 20GB SSD, 512MB RAM for $5/mo. For some reason I paid no VAT then, but I do now. Their $4/mo option now is still 512MB, still 1 vCPU, but 10GB SSD. So it's like the last decade of technological progress with regards to RAM, CPU and storage that should either lead to price cuts/spec bumps didn't happen. And yeah, DO got expensive before AI bought up all the memory.

You didn't consider inflation. 2013's $5 is $7 in today's money. Today's $4 equals roughly 2013's $2.82.

So a near 44% price reduction for a 50% reduction in only one of the components. Looks like progression to me.

Re: Migrating from DigitalOcean to Hetzner

#147

Post by airstrike »

antirez wrote: post #66
rustyhancock wrote: post #60

Earlier quoted context omitted.

Wow a Claude add embedded into a Hetzner add. How deep does this go?

"ad", with a single "d". So it's a Claude ad inside a Hetzner ad inside a decent grammar ad.

Don't forget the ad hominem

Re: Migrating from DigitalOcean to Hetzner

#148

Post by shermantanktop »

Ah yes, create db replica, promote replica to primary. Seems so simple!

When I’ve seen this work well, it’s either built into the product as an established feature, or it’s a devops procedure that has a runbook and is done weekly.

Doing it with low level commands and without a lot of experience is pretty likely to have issues. And that’s what happened here.

Re: Migrating from DigitalOcean to Hetzner

#149

Post by Aurornis »

mariopt wrote: post #128

Every time I see this kind of article, no one really bothers about sb/server redundancy, load balancers, etc. are we ok with just 1 big server that may fail and bring several services down? You saved a lot of money but you'll spend a lot of time in maintenance and future headaches.

These articles are popular where there's a mismatch between application requirements and the solution chosen. When someone over-engineers their architecture to be enterprise-grade (substitute your own definition of enterprise-grade) when really they were running a hobby project or a small business where a day of downtime every once in a while just means your customers will come back the next day, going all-out on cloud architecture is maybe not necessary. That's why you see so many comments from people arguing that downtime isn't always a big deal or that risking an outage is fine: There are a lot of applications where this is kind of true.

The confusing part about this article is the emphasis on a zero-downtime migration toward a service that isn't really ideal for uptime. It wouldn't be that expensive to add a little bit of architecture on the Hetzner side to help with this. I guess if you're doing a migration and you're paid salary or your time is free-ish, doing the migration in a zero downtime way is smart. It's a little funny to see the emphasis on zero downtime juxtaposed to the architecture they chose where uptime depends on nothing ever failing

Re: Migrating from DigitalOcean to Hetzner

#150

Post by PunchyHamster »

mariopt wrote: post #128

Every time I see this kind of article, no one really bothers about sb/server redundancy, load balancers, etc. are we ok with just 1 big server that may fail and bring several services down? You saved a lot of money but you'll spend a lot of time in maintenance and future headaches.

their original also run on single server ?

If you can tolerate few hours of downtime and some data rollback/loss, single server + robust backups can be viable strategy

Post reply on HN