If you're doing this you're using lambda's wrong.
Let me guess, you're a DynamoDB fan?
Amazon RDS Proxy for AWS Lambda
21–30 of 32 posts
Re: Amazon RDS Proxy for AWS Lambda
#22I wonder how this compares to Aurora Serverless Data API. This is an HTTP API that you POST a query to and get results data back. The result format is a bit clunky but there's all the column information you'd expect. I found this golang database interface which ended up dropping in as expected with a few tweaks. https://github.com/Clever/rds/tree/birthday My bill for Aurora Serverless Postgres last month was less tha…
We use Aurora Serverless and this is a sorely needed feature for us. We get large spikes of traffic that also cause large increases in connections to our DB, but Aurora Serverless cannot scale fast enough to cater for this. Unfortunately it doesn't seem we can enable this proxy for serverless clusters.
Re: Amazon RDS Proxy for AWS Lambda
#23For anyone else who spent 10 minutes trying to find a link to pricing from this page and failing, here it is:
https://aws.amazon.com/rds/proxy/pricing/
Free til the end of 2019, 0.015 per vCPU (of the underlying RDS instance) per hour the proxy is enabled. So it is not scaled down to 0 when not in use. For comparison, a t3.micro (2 vCPU, 1gb ram) is 0.0104 per hour. If you're a big project it might be worth it, but just keep in mind rolling your own proxy or using the RDS serverless APIs are cheaper options.
Re: Amazon RDS Proxy for AWS Lambda
#24I wonder how this compares to Aurora Serverless Data API. This is an HTTP API that you POST a query to and get results data back. The result format is a bit clunky but there's all the column information you'd expect. I found this golang database interface which ended up dropping in as expected with a few tweaks. https://github.com/Clever/rds/tree/birthday My bill for Aurora Serverless Postgres last month was less tha…
We use Aurora Serverless and this is a sorely needed feature for us. We get large spikes of traffic that also cause large increases in connections to our DB, but Aurora Serverless cannot scale fast enough to cater for this. Unfortunately it doesn't seem we can enable this proxy for serverless clusters.
Aurora serverless already has a proxy by default - if it can’t scale fast enough it’s likely because your queries are too long and interleaved to find a logical switchover point.
This proxy is probably an offshoot of the serverless proxy.
Re: Amazon RDS Proxy for AWS Lambda
#25hahaha JDBC as a service. We really needed this, what has the world come too.
You may already know all this, but I thought I’d add to what you said.
JDBC doesn’t provide connection pooling out of the box. There are connection pooling libraries that layer into JDBC. Most frameworks and application servers do bundle a connection pool out of the box.
Lambda is just a different paradigm than a single monolithic app with a connection pool. I assume that’s what you’re getting at. :)
There are other use cases though. Tools like pgBouncer are fairly useful in a large enterprise where a single database has multiple clients. They provide a single point to coordinate failovers and manage resource limits. I generally prefer a 1:1 relationship between an application and a database, but sometimes you have to play the cards you’re dealt.
Re: Amazon RDS Proxy for AWS Lambda
#26Earlier quoted context omitted.
We use Aurora Serverless and this is a sorely needed feature for us. We get large spikes of traffic that also cause large increases in connections to our DB, but Aurora Serverless cannot scale fast enough to cater for this. Unfortunately it doesn't seem we can enable this proxy for serverless clusters.
Aurora serverless already has a proxy by default - if it can’t scale fast enough it’s likely because your queries are too long and interleaved to find a logical switchover point. This proxy is probably an offshoot of the serverless proxy.
It has a hard limit on max_connections based on the "Aurora Capacity Unit", e.g. for 16 ACU's max_connections it is 2,000. We see spikes of 10x to 100x concurrent users in a matter of minutes (think hug of death style). And although our queries run fast and we see limited increase of CPU on the cluster we almost instantly hit the connection limit.
https://www.jeremydaly.com/aurora-serverless-the-good-the-ba...
Re: Amazon RDS Proxy for AWS Lambda
#27I don't understand why this isn't launching with data api support? AWS specifically built data apis into the Aurora Serverless product for this exact usecase...
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide...
If I'm using Aurora Serverless right now and want to switch over to RDS Proxy I'm going to have to rewrite my calls.
Re: Amazon RDS Proxy for AWS Lambda
#28The same functionality could have been accomplished by just allowing us to specify the max number of concurrent instances of a function that can be active at a time. With proper request queuing the problem would be solved. As usual, AWS solves a problem they failed to design for by charging for an overly complex solution. Flame me if you want but there are K8s serverless frameworks that address this out of the box.
Re: Amazon RDS Proxy for AWS Lambda
#29If you're doing this you're using lambda's wrong.
What's the right way?