So if I understand correctly, we're (economically) back at the classic model of continuously running a db in a process, right?
Not yet. Dynamodb is killing it
AWS cancels serverless Postgres service that scales to zero
51–60 of 101 posts
Re: AWS cancels serverless Postgres service that scales to zero
#52Earlier quoted context omitted.
I think the problem is that we're trying to take paradigms that are designed to be serverful (is that a word?) and shoe-horn them into working in a serverless way.
(Neon CEO). It's possible and here is the recipe: https://twitter.com/nikitabase/status/1725394843285766463
Always gotta watch what you say on Hacker News or the CEO of the company you're talking about might just arrive outta nowhere with the elbow drop of justice.
Re: AWS cancels serverless Postgres service that scales to zero
#53(CEO of neon.tech here) Scaling to zero is tricky. In order to make it work you need to 1. Separate storage and compute which aurora has done 2. Have a proxy between the user and an actual VM in which you host Postgres 3. Spin up this VM after authenticating a connection, stand up Postgres inside the VM and run the query You need to do all that very quickly- ideally in a couple hundred ms. This can only be accomplish…
Scaling from zero did use quite some seconds so there would be some leeway for an alternative implementation.
Re: AWS cancels serverless Postgres service that scales to zero
#54The title includes Postgres, but if I’m understanding correctly it’s actually both flavors of Aurora - Postgres and MySQL
Re: AWS cancels serverless Postgres service that scales to zero
#55I started using the smallest VM I can that's free. On google cloud it's 1 GB RAM, 30 GB hard drive, small CPU. I run apt install -y postgresql after I create it and run my golang app and the database ON THE SAME VM! It's amazing how much you can do with that all for free.
Best solution for small scales, doesn’t work anymore when you need reliability (unless you want to be always on call to restore from backup and are willing to accept data loss)
Re: AWS cancels serverless Postgres service that scales to zero
#56Reminder that AWS Aurora claims to have broken the CAP theorem. The literature doesn’t clarify whether they are consistent or available, and when you ask AWS directly, they tell you the CAP theorem isn’t relevant due to the way Aurora is built. They claim 99.99% availability or whatever the figure is, that it’s self healing, allows up to 2 replicas to be down for write availability and 3 replicas to be down for read…
"Amazon Aurora: Design Considerations for High Throughput Cloud-Native Relational Databases" - https://assets.amazon.science/dc/2b/4ef2b89649f9a393d37d3e04...
Re: AWS cancels serverless Postgres service that scales to zero
#57I have a feeling most people chasing "serverless" postgres or mysql with the ability to scale to zero are perfect candidates for sqlite.
Re: AWS cancels serverless Postgres service that scales to zero
#58Earlier quoted context omitted.
I think the problem is that we're trying to take paradigms that are designed to be serverful (is that a word?) and shoe-horn them into working in a serverless way.
(Neon CEO). It's possible and here is the recipe: https://twitter.com/nikitabase/status/1725394843285766463
It helps but does not fully solve it if I need PG to have 512 GB of memory buffers under load to have reasonable latency starting from 0 and going through a number of VM migrations to finally get to properly sized VM with 512 GB of hot data in memory gonna cause a ton of latency.
Re: AWS cancels serverless Postgres service that scales to zero
#59Earlier quoted context omitted.
Can’t you bypass CAP if you just have a ton of compute in the background handling all of these tasks in real time? Aurora isn’t just some binary running on ec2 it’s probably 10 different things going on
CAP is a property of any distributed system. You have to tolerate P (considering it’s distributed), so you can only be CP or AP. CP means you can’t be available, meaning your system will stop replying to queries. AP means you’re always available, but you could receive stale data when querying. It’s irrelevant whether it’s a single binary running on EC2 or a billion services working in unison. It’s a property of the s…
[deleted]
Re: AWS cancels serverless Postgres service that scales to zero
#60I guess a good opportunity for someone to build a good alternative. Although it's hard to get it right because if you scale to 0 people will complain about latency and if you don't it's not really serverless.
Corporate customers that runs AWS, GCP or Azure at not looking for alternative outside of their cloud providers. Most solution architecture are designed with the assumption that all your ressources will be inside the same vnet or subnet, in a given cloud provider. And I am not talking about any egress fees yet.