We cut our Mongo DB costs by 90% by moving to Hetzner
1–10 of 214 posts
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#2"We replaced a cluster of virtualized servers with a single bare metal server. Nothing has gone wrong, yet."
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#3I‘m a big fan of owning the stack but why not spend the money on redundancy? At least a couple of machines in a different data center at Hetzner or another provider (OVH, Scaleway, Vultr, …) can easily fit your budget.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#4"We replaced a cluster of virtualized servers with a single bare metal server. Nothing has gone wrong, yet."
There are many cases when some downtime is perfectly ok. Or, at least, worth the savings
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#5> 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 performance will be abysmal.
> When you migrate to a self-hosted solution, you're taking on more responsibility for managing your database. You need to make sure it is secure, backed up, monitored, and can be recreated in case of failure or the need for extra servers arises.
> ...for a small amount of pain you can save a lot of money!
I wouldn't call any of that "a small amount of pain." To save $3,000/month you've now required yourself to become experts in a domain that maybe is out of your depth. So whatever cost saved is now tech debt and potentially having to hire someone else to manage your homemade solution for you.
However, I self-host, and applaud other self-hosters. But sometimes it really has to make business sense for your team.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#6Always consider if 12 hours of lost revenue is worth the savings. Recently hetzner has been flakey with minimum or no response for support or even status updates that anything was wrong. My favorite was them blaming an issue on my side just to have a maintenance status update the day after about congestion.
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#7Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#8Always consider if 12 hours of lost revenue is worth the savings. Recently hetzner has been flakey with minimum or no response for support or even status updates that anything was wrong. My favorite was them blaming an issue on my side just to have a maintenance status update the day after about congestion.
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!
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#9I‘m a big fan of owning the stack but why not spend the money on redundancy? At least a couple of machines in a different data center at Hetzner or another provider (OVH, Scaleway, Vultr, …) can easily fit your budget.
We will be adding additional db servers and running our own replica set eventually. We're just not there yet. Thanks for reading!
Re: We cut our Mongo DB costs by 90% by moving to Hetzner
#10MongoDB Atlas is so overpriced that you can probably save already 90% by moving to AWS.