Live data from Hacker News

ElephantSQL Is Shutting Down

elephantsql.com

91–100 of 125 posts

Re: ElephantSQL Is Shutting Down

#91
post #41

Earlier quoted context omitted.

well, they shut this down probably because they cannot afford to keep a product that bring little revenue. I never heard of AWS retiring a product (I am excluding ancient stuff like VPC classic and SimpleDB, both had an upgrade path to something superior)

AWS is Big Tech. It locks you in, and it's not easy to guard your users' privacy against them. Smaller providers (and also local in the case of 84codes) are preferred.

> and it's not easy to guard your users' privacy against them

Source?

> Smaller providers (and also local in the case of 84codes) are preferred

AWS have a reputation and stability to keep because half of the internet, governments, banks, etc. rely on them. If a small provider makes a mistake, or goes bankrupt due to unforseen circumstances, you're left holding the bag on your own.

Re: ElephantSQL Is Shutting Down

#92

I switched to DigitalOcean and it's been a delight. $15/month for a managed Postgres is a good deal, and I am really tired of the hellscape that has become AWS configuration even for the most simplest things. Isn't the whole point of the cloud is simplicity?

What has gotten more complicated that used to be simpler in AWS?

[deleted]

Re: ElephantSQL Is Shutting Down

#93
post #91
post #41

Earlier quoted context omitted.

AWS is Big Tech. It locks you in, and it's not easy to guard your users' privacy against them. Smaller providers (and also local in the case of 84codes) are preferred.

> and it's not easy to guard your users' privacy against them Source? > Smaller providers (and also local in the case of 84codes) are preferred AWS have a reputation and stability to keep because half of the internet, governments, banks, etc. rely on them. If a small provider makes a mistake, or goes bankrupt due to unforseen circumstances, you're left holding the bag on your own.

You're being polite asking for a source. The source will, as it always does, turn out to be "some random stuff I read on the internet don't know where but everybody knows this is true".

Insert LLM-generated variation thereof.

Re: ElephantSQL Is Shutting Down

#94
post #91
post #41

Earlier quoted context omitted.

AWS is Big Tech. It locks you in, and it's not easy to guard your users' privacy against them. Smaller providers (and also local in the case of 84codes) are preferred.

> and it's not easy to guard your users' privacy against them Source? > Smaller providers (and also local in the case of 84codes) are preferred AWS have a reputation and stability to keep because half of the internet, governments, banks, etc. rely on them. If a small provider makes a mistake, or goes bankrupt due to unforseen circumstances, you're left holding the bag on your own.

If AWS goes down, and it does, you're still left holding the bag, because no one customer is important enough for them to actually support. You can leave sad voicemails for your customer account representative, and pretty much nothing else.

The idea of AWS as some kind of bag-holding partner is risible. They're a machine that helps convert capex to opex. Any systems services they may offer along the way are purely secondary.

Re: ElephantSQL Is Shutting Down

#95

This might help people when looking for an alternative. https://wheretohostmy.app/?tech=%5B%22postgresql%22%5D It's a side project I'm currently building so hearing some feedback is highly appreciated.

Fly.io also seems to be missing. Great for Elixir and Rails. Pretty great Heroku replacement

Re: ElephantSQL Is Shutting Down

#96

I switched to DigitalOcean and it's been a delight. $15/month for a managed Postgres is a good deal, and I am really tired of the hellscape that has become AWS configuration even for the most simplest things. Isn't the whole point of the cloud is simplicity?

>Isn't the whole point of the cloud is simplicity? Maybe for a few cloud offerings, but not for cloud in general. I think the point of the cloud is that businesses can exchange employees for services, and shift some of the maintenance responsibility. No service is for the people who actually interact with it. It's for the ones that pay for it.

No, for example, I couldn’t manage a database as well as RDS and I wouldn’t want to, I don’t believe I could hire the several people required to replicate what RDS can do as well as RDS can do it.

The primary benefit of cloud though is that you don’t have to fight for or wait for capital expenditure budgets to grow, you don’t have to wait for hardware to arrive, you don’t have to negotiate with vendors, you don’t have to fight about how long you should keep old hardware or replace it, you don’t have to deal at all with the political or business aspects of managing millions of dollars of hardware.

I can just go on a website and click a few buttons and have something new, and the biggest argument about it is a yearly cloud budget discussion.

Re: ElephantSQL Is Shutting Down

#97
post #91
post #41

Earlier quoted context omitted.

AWS is Big Tech. It locks you in, and it's not easy to guard your users' privacy against them. Smaller providers (and also local in the case of 84codes) are preferred.

> and it's not easy to guard your users' privacy against them Source? > Smaller providers (and also local in the case of 84codes) are preferred AWS have a reputation and stability to keep because half of the internet, governments, banks, etc. rely on them. If a small provider makes a mistake, or goes bankrupt due to unforseen circumstances, you're left holding the bag on your own.

Whit AWS you probably have to hire a decent engineer who knows how to build stuff the right way (never touch the dashboards, do all through well-tested, declarative, repeatable IaaC, set up proper replication and backups, preemptively simulating the outages, and so on).

But unless you need a complex control plane or highly dynamic scaling on a daily basis you also can do exact same thing with any non-cloud provider (and a CDN). Order some bare metal, roll out, enjoy - if it goes bad, order bare metal from someone else, redeploy to it, restore from backups, and recover in about the same time (half a day) it takes AWS to fix us-east-1 when it fails. It also probably will save a lot of money (NATgw bills alone) in the long term.

Re: ElephantSQL Is Shutting Down

#98
post #95

This might help people when looking for an alternative. https://wheretohostmy.app/?tech=%5B%22postgresql%22%5D It's a side project I'm currently building so hearing some feedback is highly appreciated.

Fly.io also seems to be missing. Great for Elixir and Rails. Pretty great Heroku replacement

I use Gigalixir to host Elixir apps. It's more or less a drop-in Heroku replacement and it's worked really well for me.

Re: ElephantSQL Is Shutting Down

#99

Earlier quoted context omitted.

>Isn't the whole point of the cloud is simplicity? Maybe for a few cloud offerings, but not for cloud in general. I think the point of the cloud is that businesses can exchange employees for services, and shift some of the maintenance responsibility. No service is for the people who actually interact with it. It's for the ones that pay for it.

No, for example, I couldn’t manage a database as well as RDS and I wouldn’t want to, I don’t believe I could hire the several people required to replicate what RDS can do as well as RDS can do it. The primary benefit of cloud though is that you don’t have to fight for or wait for capital expenditure budgets to grow, you don’t have to wait for hardware to arrive, you don’t have to negotiate with vendors, you don’t hav…

I completely agree. I see this point in cloud too, and this is really missing from my original comment. Cloud is a huge enabler, and basically 0 upfront cost.

Re: ElephantSQL Is Shutting Down

#100

How does one handle a zero downtime migration in this case? On a database of 50gib+ is this a solved problem in Postgres world?

gov.uk did a good writeup of their 11 second migration of a 400gb database with ~1000 read/writes per second: https://gds.blog.gov.uk/2024/01/17/how-we-migrated-our-postg... With their approach, there would always be a minimum of 1 second downtime from the DNS changeover.

Great write-up; their minimum would be O(DNS_SWAP + REPLICATION_LAG), though, so ~11s, if DMS 10s delay holds!
Post reply on HN