> Cloud providers are expensive for steady-state workloads. Asking the obvious question: why not your own server in a colo?
Bit of waste of time for a server. Only makes sense if you actually need at least half a rack
Migrating from DigitalOcean to Hetzner
161–170 of 454 posts
Re: Migrating from DigitalOcean to Hetzner
#162Every 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.
A lot of things don't need that.
Also, don't underestimate the reliability of simplicity.
I was a Linux sysadmin for many years, and I have never seen as much downtime from simpler systems as I routinely see from the more complicated setups. Somewhere between theory and reality, simpler systems just comes out ahead most of the time.
Re: Migrating from DigitalOcean to Hetzner
#163> Cloud providers are expensive for steady-state workloads. Asking the obvious question: why not your own server in a colo?
“Your own server in a colo” means going to the colo to swap RAM or an SSD when something goes wrong. You rent a server and the benefit is the rentor has spare parts on hand and staff to swap parts out.
So on average once or twice per 5 years per server. Remote hands are also service you can pay for.
Most expense is initial setup and automation, but once you get thru that hump and have non-spiky loads it can be massively cheaper
Re: Migrating from DigitalOcean to Hetzner
#164Re: Migrating from DigitalOcean to Hetzner
#165Earlier quoted context omitted.
> they could They could, but they didn't and instead they wrote that blog post which, even being generous is still kinda hard to avoid describing as misleading. I would not have written the post I did if they had presented a multi-node bare-metal cluster or whatever more realistic config.
> They could, but they didn't and instead they wrote that blog post which, even being generous is still kinda hard to avoid describing as misleading. What do you feel was misleading?
> What do you feel was misleading?
Erm. I already spelt it out in my original post ?
I'm not going to re-write it, the TL;DR is they are making an Apples and Oranges comparison.
Yes they "saved money" but in no way, shape or form are the two comparable.
The polite way to put is is .... they saved as much money as they did because they made very heavy handed "architectural decisions". "Decisions" that they appear to be unaware of having made.
Re: Migrating from DigitalOcean to Hetzner
#166Earlier quoted context omitted.
> they could They could, but they didn't and instead they wrote that blog post which, even being generous is still kinda hard to avoid describing as misleading. I would not have written the post I did if they had presented a multi-node bare-metal cluster or whatever more realistic config.
> They could, but they didn't and instead they wrote that blog post which, even being generous is still kinda hard to avoid describing as misleading. What do you feel was misleading?
That they get the exact same level of service for $1,199 less per month.
They don't.
And reading the article, they don't seem to understand that.
Re: Migrating from DigitalOcean to Hetzner
#167Every 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.
It depends on the service and how critical that website is. Sometimes it's completely acceptable that a server will run for 10 years with say 1 week or 1 month of downtime spread over those 10 years, yes. That's the sort of uptime you can see with single servers that are rarely changed and over-provisioned as many on Hetzner are. Some examples: Small businesses where the website is not core to operations and is more…
What struck me though is that OP did so much work to migrare the server with zero downtime. The _single_ big server. Something’s off here.
Re: Migrating from DigitalOcean to Hetzner
#168I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…
Not every fscking story has to be about AI.
You may not be interested in AI, but AI is interested in you.
Re: Migrating from DigitalOcean to Hetzner
#169AWS only requires a card from me. I tried registering at Hetzner and they wanted a picture of my passport.
That's a trend which is more and more common nowadays. I wish the industry would adopt more zero knowledge methods in this regards. They are existing and mathematically proven but it seems there is no real adoption. - OpenAI wants my passport when topping up 100 USD - Bolt wanted recently my passport number to use their service - Anthropic seems wants to have passports for new users too - Soon age restriction in OS o…
I dont. I'm happy the grift economy has some controls on it. As much as I love open source and all the efforts in collective without government interference; some security is required, otherwise we'll just invite more grift based economics.
It's bad enough living in America without the rest of the world adopting the grift economy.
Re: Migrating from DigitalOcean to Hetzner
#170Can someone tell me the AWS server cost with the same spec? Probably $5000 per month?