Live data from Hacker News

ElephantSQL Is Shutting Down

elephantsql.com

51–60 of 125 posts

Re: ElephantSQL Is Shutting Down

#51
post #39

Earlier quoted context omitted.

I had good experience with Aiven in the past, we needed something located in the EU: https://aiven.io/

It's more expensive than AWS RDS and Google Cloud SQL, but their service seems more comprehensive, with fast major version upgrade, multi-cloud deployment and built-in PgBouncer integration. For business critical operations, it is probably worth it.

They also have (or had? That was a few years ago) pretty good support

Re: ElephantSQL Is Shutting Down

#52
post #23

Earlier quoted context omitted.

From what the migration doc says, it will only support pgdump migration. Meaning it will require downtime, or at least write downtime. Create backup using pgdump, restore the dump to new database. While making sure no changes to the old db before switch over.

Ouch that will make migrating anything over a few hundred gigs almost impossible. Our postgres db is about 2TB and pgdump stopped being viable a long time ago.

> Our postgres db is about 2TB and pgdump stopped being viable a long time ago.

Due to the time it takes to export, or because it can't handle a database of that size at all?

Re: ElephantSQL Is Shutting Down

#53
post #32

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)

I assume AWS fully automates their stuff so the maintenance is ~0 outside their normal datacenter and SRE stuff which amortizes the total cost to ~0, so why retire a service? Just stop development.

[flagged]

Re: ElephantSQL Is Shutting Down

#54
post #5

Earlier quoted context omitted.

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

What? RDS supports username+password authentication for the database connection

That’s true, though you have to engage with the behemoth to get to that point.

Re: ElephantSQL Is Shutting Down

#56
post #5

Earlier quoted context omitted.

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

Care to elaborate?

Not OP but even setting up an AWS Account is a roughly hundred step process. Root account, IAM Accounts, I just tried using CLIv2 which asked me to set up something called Identity center first? Billing is complicated, setting up looking and metrics... Another two services. Some other best practice things... Also extra services. AWS is complicated. There is - for me and seemingly others - a lot of value in avoiding this complexity. AWS used to be easy to use for "drive by users". It's not anymore.

Re: ElephantSQL Is Shutting Down

#58
post #42
post #33

Earlier quoted context omitted.

Is there any plans to offer your manager service at Digital Ocean / Vultr in the US?

We are planning to open up US regions quite soon but we are mostly focusing on bare metal providers at this point so Digital Ocean is out of picture.

Starting with Hetzner US then?

Re: ElephantSQL Is Shutting Down

#59
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.

Evidently not, as few are willing to pay a large premium for them.

Evidently? Clarify please.

Re: ElephantSQL Is Shutting Down

#60

Earlier quoted context omitted.

Care to elaborate?

Not OP but even setting up an AWS Account is a roughly hundred step process. Root account, IAM Accounts, I just tried using CLIv2 which asked me to set up something called Identity center first? Billing is complicated, setting up looking and metrics... Another two services. Some other best practice things... Also extra services. AWS is complicated. There is - for me and seemingly others - a lot of value in avoiding t…

Well put, that's in essence what I meant.

If you are using AWS anyway and are accustomed to it, obviously, RDS is a good choice. But I don't want to learn what DNS and Filesystem are called in AWS-speak just to shoehorn myself into getting stuck with AWS forever, when all I need is a hosted database so I don't have to worry about backups, etc.

My typical situation sees small to medium (virtual) servers that run software for tens to possibly thousands of users. There are plenty of use cases that aren't "google scale" and can be operated on a simple machine and can profit from a "simple" hosted DB.

Rant: Same goes for things like CDNs, I'd guess that 99% of websites don't get nearly the amount of traffic that a simple linux server couldn't handle out of the box. Let alone need sub 100ms ping responses, yet there is this weird cargo cult that requires putting your terraformed, docker stuff running javascript from with a python container with multiple layers of caching behind cloudflare because people don't dare consider simple architectures.

Post reply on HN