Reputation: 355
Connection pools on AWS lambda
I have a lambda that is currently deployed on AWS. It is a simple piece of CRUD logic which sits behind a an API gateway.
The problem I am currently facing is that as soon as there is a peak in traffic the connections on my database shoot up.
I understand that this is due to the parallel invocation of many lambdas together, and opening their separate connections, but is there a way I can do some sort of connection pooling here?
The below thread states that I can(If I code a bit intelligently do some sort of a connection pool in a container):
How we can use JDBC connection pooling with AWS Lambda?
But it does not guarantee anything.
Can I do something about this in my lambda or do I have to use an external connection pooler for this(I use Postgres, so that should be pg_bouncer)?
Upvotes: 1
Views: 1680
Answers (1)
Related Questions
- sql.DB on aws-lambda too many connection
- Connection pooling in AWS across lambdas
- Handling AWS RDS Connection Pooling (with POSTGRES 13) and Node Lambdas
- Q. AWS lambda - Share database connection pool between lambda functions
- How we can use JDBC connection pooling with AWS Lambda?
- Serverless Database Connection Pooling
- AWS Lambda RDS Database Connection Pooling
- Connection Pooling in AWS Lambda with RDS?
- Using mysql pool on amazon lambda
- Connection Pooling with PostgreSQL and AWS