4 ms·

Aws might have fixed this by now with severless aurora, but as of earlier this year the issue was connection pools didn’t work on lambda functions due to their

Aws might have fixed this by now with severless aurora, but as of earlier this year the issue was connection pools didn’t work on lambda functions due to their ephemeral nature not being able to keep the tcp sockets open for more than a few minutes before the functions froze or were terminated.

pavelrub 8y ago
Connection pools always worked quite well with Lambdas, as long as the connection pool was initiated in the global scope of the running code, and not within the handler function. See [1] and [2] [1] - https://docs.aws.amazon.com/lambda/latest/dg/running-lambda-code.html https://docs.aws.amazon.com/lambda/latest/dg/running-lambda-... [2] - https://blog.spotinst.com/2017/11/19/best-practices-serverless-connection-pooling-database/ https://blog.spotinst.com/2017/11/19/best-practices-serverle...
dlhavema 8y ago
We use pools in lambdas to Amazon Aurora and it works out fine. Only limit we hit was when the db server was configured way too small.
- zedpm 8y ago
  Are you running your Lambdas inside the VPC (and incurring huge cold-start latency), or are you running your database exposed to the public internet? I've avoided using Lambda for anything that requires relational database connectivity because those appear to be the two options, and neither is viable for me.
scarface74 8y ago
The Data API was announced less than a month ago. https://aws.amazon.com/about-aws/whats-new/2018/11/aurora-serverless-data-api-beta/ https://aws.amazon.com/about-aws/whats-new/2018/11/aurora-se...