Migrating from AWS to Hetzner
241–250 of 643 posts
Re: Migrating from AWS to Hetzner
#242I 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
#243Earlier quoted context omitted.
> 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.
The benefit of cloud has always been that it allows the company to trade capex for opex. From an engineering perspective, it trades scalability for complexity, but this is a secondary effect compared to the former tradeoff.
Re: Migrating from AWS to Hetzner
#244Re: Migrating from AWS to Hetzner
#245There's a value curve for infrastructure, I'll use an analogy... Low Cost High Cost ============================================================== FARM WHOLESALER GROCERY RESTAURANT DOORDASH BUILD CO-LOCATION HETZNER AWS VERCEL While it's not a perfect analogy, in principle it holds true. As such, it should come as no surprise that eating at a restaurant every day is going to be way more expensive.
I hadn't seen your comment when I wrote this, below: https://news.ycombinator.com/item?id=45616366
I love your farm-to-table grid: works for everyone not just HN commenters. And putting DOORDASH on the right is truer from cost perspective than the metaphor I'd used.
For HN, I'd compared to a pricing grid (DIY, Get Started, Pro, Team, Enterprise) with the bottom line that if YAGNI, don't choose it.
Your grid emphasizes my other point, it's about your own labor.
Re: Migrating from AWS to Hetzner
#246Hetzner 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…
Re: Migrating from AWS to Hetzner
#247The public cloud is priced as if availability, reliability, durability, and latency matter to your business. If they don't, you can get far with just a single machine. A great deal of the work in cloud engineering is ensuring the abstractions meet the service guarantees. Similarly you can make a car much cheaper if you don't need to guarantee the driver will survive a collision. The cost of providing a safety guarant…
You do know you can have high availability without using cloud providers? E.g. you run a second server in a different database as a standby that can take over, etc.
IF you need it, soon you wish the lego blocks pulled IAM all the way through and worked with a common API