3 ms·
Is using Lambda with an external data store (like MongoDB) a solved problem? I remember this being an issue a long time ago, where Lambda pretty much was a non
by cj 3y ago
Is using Lambda with an external data store (like MongoDB) a solved problem?
I remember this being an issue a long time ago, where Lambda pretty much was a non starter for use cases where you're running 1000 independent tasks that each, on their own, is a small unit of work (just 1 or 2 database queries).
Long way of asking: is there a way to share a database connection between lambda functions or does each run need to re-establish / re-authenticate a new connection with the database?
- josevalerio 3y agoDeclare your connection outside of your handler function - this post is from 2017 but it shows it clearly: https://www.jeremydaly.com/reuse-database-connections-aws-lambda/ https://www.jeremydaly.com/reuse-database-connections-aws-la... It will get re-used across lambda invocations as long as the instance of it isn't killed which typically happens after a few minutes
- alexbevi 3y agoFor MongoDB specifically see the best practices docs for Lambda (https://www.mongodb.com/docs/atlas/manage-connections-aws-lambda/ https://www.mongodb.com/docs/atlas/manage-connections-aws-la...). This outlines creating the handler outside the function context to allow the client to be reused between invocations.