I’m starting to worry about this Hetzner trend. It can end up to get the price skyrocketing.
There's other providers (OVH, etc) so I'm sure the price will remain competitive
We cut our Mongo DB costs by 90% by moving to Hetzner
31–40 of 214 posts
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#32I’m starting to worry about this Hetzner trend. It can end up to get the price skyrocketing.
Hopefully not. Their console is pretty bad so I reckon that will put a lot of people off.
The cloud console is pretty good though? Even does live sync!
The old one for dedicated servers (robot) is horribly outdated though.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#33I’m starting to worry about this Hetzner trend. It can end up to get the price skyrocketing.
We’re just going to end up with everyone moving from Amazon to Hetzner and the same issue will remain. High prices, lockin, etc will appear.
We need an American “get off American big tech” movement.
Differentiate people! Reading “we moved from X to Y” does not mean everyone move from X to Y, it means start considering the Y values and research other Y’s around you.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#34How long does mongodump take on that database? My experience was that incremental filesystem/blockdevice snapshots were the only realistic way of backing up (non sharded) mongodb. In our case EBS snapshots, but I think you can achieve the same using LVM or filesystems like XFS and ZFS.
It takes ~21hrs to dump the entire db (~500gb), but I'm limited by my internet speed (100mbps, seeing 50-100mbps during dump). Interestingly, the throughput is faster than doing a db dump from atlas which used to max around 30mbps
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#35You probably want to store the backup somewhere else, ie. not Hetzner. They are known to just cancel accounts and cut access.
Any proof of that? I am a Hetzner customer and had never heard of this before. Would be good to know what I got into.
A few years back I launched an io game and used hetzner as my backend. an hour into launch day they null routed my account because their anti-abuse system thought my sudden surge in websocket connections was an attack (unclear if they thought it was inbound or outbound doing the attacking).
I had paid for advertising on a few game curation sites plus youtubers and streamers. Lovely failure all thanks to Hetzner. Took 3 days and numerous emails with the most arrogant Germans you’ve ever met before my account was unlocked.
I switched to OVH and while they’re not without their own faults (reliability is a big one), it’s been a far better experience.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#36Earlier quoted context omitted.
Atlas wasn't giving us any support for $3K per month. Hetzner at least have some channel to contact them, which is an improvement. That said, if their uptime is rubbish them we'll probably migrate again. Moving back to Atlas is not an option as we were getting hammered by the data transfer costs and this was only going to increase due to our architecture. Thanks for reading!
500GB isn't a lot of data, and $3K/month seems like an extortion for that little data. Having said that, MongoDB pricing page promises 99.995% uptime, which is outstanding, and would probably be hard to beat that doing it oneself, even after adding redundancy. But maybe you don't need that much uptime for your particular use case.
Its more like 700GB now on the new server and we were about to have to migrate to a higher tier on Atlas.
> maybe you don't need that much uptime for your particular use case.
Correct. Thanks for reading!
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#37> The more keen eyed among you will have noticed the huge cost associated with data transfer over the internet - its as much as the servers! We're building Prosopo to be resilient to outages, such as the recent massive AWS outage, so we use many different cloud providers. I mean, you're connecting to your primary database potentially on another continent? I imagine your costs will be high, but even worse, your perfor…
> I mean, you're connecting to your primary database potentially on another continent? Atlas AWS was actually setup in Ireland. The data transfer costs were coming from extracting data for ML modelling. We don't get charged for extracting data with the new contract. > experts in a domain that maybe is out of your depth We're in the bot detection space so we need to be able to run our own infra in order to inspect con…
aww shucks ;)
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#38As in so many of these stories, what gets glossed over is just how much complexity there is in setting up your own server securely.
You set up your server. Harden it. Follow all the best practices for your firewall with ufw. Then you run a Docker container. Accidentally, or simply because you don’t know any better, you bind it to 0.0.0.0 by doing 5432:5432. Oops. Docker just walked right past your firewall rules, ignored ufw, and now port 5432 is exposed with default Postgres credentials. Congratulations. Say hello to Kinsing.
And this is just one of many possible scenarios like that. I’m not trying to spread FUD, but this really needs to be stressed much more clearly.
EDIT. as always - thank you HN for downvoting instead of actually addressing the argument.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#39You probably want to store the backup somewhere else, ie. not Hetzner. They are known to just cancel accounts and cut access.
Any proof of that? I am a Hetzner customer and had never heard of this before. Would be good to know what I got into.
There are a lot of such stories if you go digging around HN and reddit threads. Haven't seen a lot of these stories in a while, so it may be happening less now.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#40Earlier quoted context omitted.
Hopefully not. Their console is pretty bad so I reckon that will put a lot of people off.
The cloud console is pretty good though? Even does live sync! The old one for dedicated servers (robot) is horribly outdated though.
Ah right, we're on robot so I've not seen the cloud one. Robot is old! :)