Live data from Hacker News

ElephantSQL Is Shutting Down

elephantsql.com

1–10 of 125 posts

Re: ElephantSQL Is Shutting Down

#3
This makes sense, but also not surprised.

In today's world there are countless Postgres providers (Supabase, RDS, DigitalOcean, GCP, Azure, etc) so there is plenty of choice now.

Although I don't see why anyone would choose niche providers today other than the cloud provided ones like RDS now.

Re: ElephantSQL Is Shutting Down

#4
What a shame. This is "cloud" as it ought to be: be clear about the service you provide, provide it well, no lock in. Simple and matter-of-factly.

I just started evaluating them about a month ago, loved their hosted postgres and a couple of days later the EOL announcement poped up in my dashboard :(

Re: ElephantSQL Is Shutting Down

#5

This makes sense, but also not surprised. In today's world there are countless Postgres providers (Supabase, RDS, DigitalOcean, GCP, Azure, etc) so there is plenty of choice now. Although I don't see why anyone would choose niche providers today other than the cloud provided ones like RDS now.

Because RDS forces you to deal with the AWS behemouth instead if just changing your database connect parameters.

Re: ElephantSQL Is Shutting Down

#7
post #5

This makes sense, but also not surprised. In today's world there are countless Postgres providers (Supabase, RDS, DigitalOcean, GCP, Azure, etc) so there is plenty of choice now. Although I don't see why anyone would choose niche providers today other than the cloud provided ones like RDS now.

Because RDS forces you to deal with the AWS behemouth instead if just changing your database connect parameters.

Care to elaborate?

Re: ElephantSQL Is Shutting Down

#8
post #5

This makes sense, but also not surprised. In today's world there are countless Postgres providers (Supabase, RDS, DigitalOcean, GCP, Azure, etc) so there is plenty of choice now. Although I don't see why anyone would choose niche providers today other than the cloud provided ones like RDS now.

Because RDS forces you to deal with the AWS behemouth instead if just changing your database connect parameters.

I would argue there is limited/no market for Database as a Service where the database isn’t hosted on the same cloud provider and region as your application. Egress costs way too much for that.

So you’d assume most people are already dealing with the AWS behemoth.

And if the cloud provider is providing a competing Database as a Service then it’s almost impossible to compete.

Post reply on HN