I love how few comments on this and similar posts give much context along with their advice. Are you hosting a church newsletter in your spare time or a resource intensive web app with millions of paying enterprise customers and a dedicated dev ops team in 3 continents? Any advice on price / performance / availability is meaningless unless you explain where you're coming from. The reason we see people overcomplicatin…
Migrating from AWS to Hetzner
341–350 of 643 posts
Re: Migrating from AWS to Hetzner
#342I cannot overstate the performance improvement of deploying onto bare metal. We typically see a doubling of performance, as well as extremely predictable baseline performance. This is down to several things: - Latency - having your own local network, rather than sharing some larger datacenter network fabric, gives around of order of magnitude reduced latency - Caches – right-sizing a deployment for the underlying har…
Ya but then you need to pay for a team to maintain network and continually secure and monitor the server and update/patch. The salaries of those professionals , really only make sense for a certain sized organization. I still think small-midsized orgs may be better off in cloud for security / operations cost optimization.
Re: Migrating from AWS to Hetzner
#343You stop worrying about S3 vs EFS vs FSx, or Lambda cold starts, or EBS burst credits. You just deploy a Docker stacks on a fast NVMe box and it flies. The trade-off is you need a bit more DevOps discipline: monitoring, backups, patching, etc. But that's the kind of stuff that's easy to automate and doesn't really change week to week.
At Elestio we leaned into that simplicity, we provide fully managed open-source stacks for nearly 400 software and also cover CI/CD (from Git push to production) on any provider, including Hetzner.
More info here if you're curious: https://elest.io
(Disclosure: I work at Elestio, where we run managed open-source services on any cloud provider including your own infra.)
Re: Migrating from AWS to Hetzner
#344Earlier 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.
Yeah I always just kinda laugh at these comparisons, because it's usually coming from tech people who don't appreciate how much more valuable people's time is than raw opex. It's like saying, you know it's really dumb that we spend $4000 on Macbooks for everyone, we could just make everyone use Linux desktops and save a ton of money.
You are self-managing expensive dedicated hardware in form of MacBooks, instead of renting Azure Windows VM's?!
Shame!
Re: Migrating from AWS to Hetzner
#345I 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 recently rediscovered this website that might help: https://vpspricetracker.com Too cool to not share, most of the providers listed there have dedicated servers too.
Re: Migrating from AWS to Hetzner
#346Earlier quoted context omitted.
They conveniently provide no detail about the usecase, so it's hard to tell But, yeah, there's certainly a solution to provide better performances for cheaper, using other settings/services on AWS
We're hoping to write a case study down the road that will give more detail. But the short version is that not all parts of the client's organisation have aligned skills/incentives. So sometimes code is deployed that makes, shall we say, 'atypical use' of the resources available. In those cases, it is great to a) not get a shocking bill, and b) be able to somewhat support this atypical use until it can be remedied.
I'm honestly quite interested to learn more about the usecase that required those 50k API calls!
I've seen a few cases of using S3 for things it was never intended for, but nothing close to this scale
Re: Migrating from AWS to Hetzner
#347Earlier 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.
Re: Migrating from AWS to Hetzner
#348Earlier quoted context omitted.
What is old is new again. My employer is so conservative and slow that they are forerunning this Local Cloud Edge Our Basement thing by just not doing anything.
> What is old is new again. Over the years I tried occasionally to look into cloud, but it never made sense. A lot of complexity and significantly higher cost, for very low performance and a promise of "scalability". You virtually never need scalability so fast that you don't have time to add another server - and at baremetal costs, you're usually about a year ahead of the curve anyways.
Re: Migrating from AWS to Hetzner
#349Startup founders and employees are you really paying insane bills to AWS? How? We are really paying peanuts compared to other expenses.
Re: Migrating from AWS to Hetzner
#350Earlier quoted context omitted.
> If you don't want to do this yourself, then we'll do it for you for half the price of AWS (and we'll be your DevOps team too You might not realize but you are actually increasing the business case for AWS :-) Also those hardware savings will be eaten away by two days of your hourly bill. I like to look at my project costs across all verticals...
> Also those hardware savings will be eaten away by two days of your hourly bill Doubt it. I've personally seen AWS bills in the tens of thousands, he's probably not that costly for a day.
Biggest recent ones were ~200k and ~100k that we managed to lower to ~80k with a couple months of work (but it went back up again after I left).
I fondly remember lowering our Heroku bill from 5k to 2k back in 2016 after a day of work. Management was ecstatic.