Amazon RDS Proxy for AWS Lambda

Post by pavelrub » Thu, Dec 05, 2019, 12:10 PM UTC

foo4u wrote: post #28

The 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.

Specifying the max number of concurrent lambda execution has been possible for years - it's called reserved concurrency.

This does nothing to solve the issue however. There are many use cases where you can't delay handling requests.

Post by ocdnix » Thu, Dec 05, 2019, 12:16 PM UTC

Znafon wrote: post #16

ocdnix wrote: post #8

Earlier quoted context omitted.

I really hope it can replace PgBouncer. We've spent way too much time getting it running in ECS, mostly due to us needing a separate PgBouncer service for the primary and replica RDS instances. And then a third ECS service running HAProxy in TCP mode to load balance between the PgBouncer services, to provide a read-only endpoint that balances between the primary and replica. Add issues like: having to patch in HAProx…

Why did you not use ECS with EC2 instead of patching HAProxy? With the Amazon AMI it is pretty straightforward.

If I were to do it again, I'd consider either that or building it directly on EC2, preparing the AMI with Packer or something, and handling scaling with an autoscaling group.

Re: Amazon RDS Proxy for AWS Lambda

Re: Amazon RDS Proxy for AWS Lambda