News for hackers. Stuff that matters.
Re:AWS Lambda – Best practices by scarhill on Thursday March 02, 2017 @09:49AM (#13774306)
Right, but only one request can be in progress against a container at a time, correct? So there's no reason for your pool to allow more than one connection. Of course, that might still be useful for retry, etc. if the connection went away while the container was frozen.
Re:AWS Lambda – Best practices by throwaway2016a on Thursday March 02, 2017 @10:17AM (#13774573)
It would be a pool of just one connection per database endpoint. So pool in the sense that once a stateless function is done with it it becomes available again for another function to take it. But you don't need multiple connections of the same type in the pool.