Cached Mongodb connection - Global variable

Hi guys,

I’m using aws-serverless-express repository for a project, and I’m trying to optimize Mongodb connection when Lambda function is awakened.

Currently, for each call, my function create a new Mongodb connection (too bad…), and I found this solution: keep in global variable, the Mongodb connection.

(Full article: https://blog.cloudboost.io/i-wish-i-knew-how-to-use-mongodb-connection-in-aws-lambda-f91cd2694ae5)

But I don’t know how to do that with my current architecture code:

"use strict";
const awsServerlessExpress = require("aws-serverless-express");
const app = require("./app");

const binaryMimeTypes = [
  "application/javascript",
  "..."
];
const server = awsServerlessExpress.createServer(app, null, binaryMimeTypes);

exports.handler = (event, context) => awsServerlessExpress.proxy(server, event, context);

Currently my Mongodb connection is done in app.js file. So each call reload app.js file… I’m looking for a solution to send my Mongodb variable to my file app and keep alive Mongodb connection while Lambda function is awakened.

Thanks for your help.

[yottachen]

I used lodash-memoize to cache the function. This solved my problem. Here is my code example, if someone is interested.

// index.js

const containerId = Date.now().toString().slice(-6);

exports.handler = async (event) => {
    const generate = require('./generator.js');
    console.log(`ContainerId: ${containerId}`);
    generate('clientId1');
    generate('clientId2');
    generate('clientId1');
    generate('clientId2');
};


// generate.js
const memoize = require('./memoize');

const getClientSecret = (clientId) => {
    console.log('hello');
    return clientId;
};

const cachedSecret = memoize(getClientSecret);

const generate = (clientId) => {
    const cs = cachedSecret(clientId);
    console.log(cs);
    return cs;
};

module.exports = generate ;

//memoize.js is lodash-memoize source code. I just use the source code here. 

The result looks like this:

// First trigger lambda
ContainerId: 071040
hello
clientId1
hello
clientId2
clientId1
clientId2

// Second time to trigger lambda
ContainerId: 071040
clientId1
clientId2
clientId1
clientId2

What I found:

• Lambda will run in same container if you run it continuously.
• No need to use NodeJS global variable. Lodash-memoize will cache getClientSecret function.

[brettstack]

You should be fine. app.js will only be loaded once per Lambda container (or “cold start”)