DB Connection Management in AWS Lambda functions
I am using AWS Lambda to build out my API. I decided to go with a monolith architecture to minimize cold starts. I'm using express.js for routing and the mysqljs library to connect to my database. The API is into different folders: routes, controllers and models:
my-app
├── index.js
├── controllers
├── models
└── routes
I'm using the serverless framework and serverless-offline for local development.
One problem I have been having is with my database connection pools. And I think the problem is because serverless-offline and lambda functions behave differently and in ways I don't fully understand. I have gone through several different approaches.
The current is I create the pool in index.js, inside the exports.handler, and then pass it to the routes, which passes it to the routes, which passes it to the controllers which passes it to the models. When the model returns the to the controller and I call res.json() and pool.end().
This works well in serverless-offline, but when I call the API from inside the Lambda function, the first time it works fine, but the second time I get Cannot enqueue Query after invoking quit. I thought every API call would be a new 'invocation'.
amazon-web-services aws-lambda serverless-framework
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
add a comment |
I am using AWS Lambda to build out my API. I decided to go with a monolith architecture to minimize cold starts. I'm using express.js for routing and the mysqljs library to connect to my database. The API is into different folders: routes, controllers and models:
my-app
├── index.js
├── controllers
├── models
└── routes
I'm using the serverless framework and serverless-offline for local development.
One problem I have been having is with my database connection pools. And I think the problem is because serverless-offline and lambda functions behave differently and in ways I don't fully understand. I have gone through several different approaches.
The current is I create the pool in index.js, inside the exports.handler, and then pass it to the routes, which passes it to the routes, which passes it to the controllers which passes it to the models. When the model returns the to the controller and I call res.json() and pool.end().
This works well in serverless-offline, but when I call the API from inside the Lambda function, the first time it works fine, but the second time I get Cannot enqueue Query after invoking quit. I thought every API call would be a new 'invocation'.
amazon-web-services aws-lambda serverless-framework
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
Its weird: on Lambda, when I require the pool from the database.js file, it gives a reference to the same object. In local, it gives me a new pool object
– Jack Pilowsky
Nov 17 '18 at 11:08
Related topic: jeremydaly.com/reuse-database-connections-aws-lambda
– jarmod
Nov 19 '18 at 3:02
add a comment |
I am using AWS Lambda to build out my API. I decided to go with a monolith architecture to minimize cold starts. I'm using express.js for routing and the mysqljs library to connect to my database. The API is into different folders: routes, controllers and models:
my-app
├── index.js
├── controllers
├── models
└── routes
I'm using the serverless framework and serverless-offline for local development.
One problem I have been having is with my database connection pools. And I think the problem is because serverless-offline and lambda functions behave differently and in ways I don't fully understand. I have gone through several different approaches.
The current is I create the pool in index.js, inside the exports.handler, and then pass it to the routes, which passes it to the routes, which passes it to the controllers which passes it to the models. When the model returns the to the controller and I call res.json() and pool.end().
This works well in serverless-offline, but when I call the API from inside the Lambda function, the first time it works fine, but the second time I get Cannot enqueue Query after invoking quit. I thought every API call would be a new 'invocation'.
amazon-web-services aws-lambda serverless-framework
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
I am using AWS Lambda to build out my API. I decided to go with a monolith architecture to minimize cold starts. I'm using express.js for routing and the mysqljs library to connect to my database. The API is into different folders: routes, controllers and models:
my-app
├── index.js
├── controllers
├── models
└── routes
I'm using the serverless framework and serverless-offline for local development.
One problem I have been having is with my database connection pools. And I think the problem is because serverless-offline and lambda functions behave differently and in ways I don't fully understand. I have gone through several different approaches.
The current is I create the pool in index.js, inside the exports.handler, and then pass it to the routes, which passes it to the routes, which passes it to the controllers which passes it to the models. When the model returns the to the controller and I call res.json() and pool.end().
This works well in serverless-offline, but when I call the API from inside the Lambda function, the first time it works fine, but the second time I get Cannot enqueue Query after invoking quit. I thought every API call would be a new 'invocation'.
amazon-web-services aws-lambda serverless-framework
amazon-web-services aws-lambda serverless-framework
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
asked Nov 17 '18 at 10:25
Jack Pilowsky
1,15851831
1,15851831
Its weird: on Lambda, when I require the pool from the database.js file, it gives a reference to the same object. In local, it gives me a new pool object
– Jack Pilowsky
Nov 17 '18 at 11:08
Related topic: jeremydaly.com/reuse-database-connections-aws-lambda
– jarmod
Nov 19 '18 at 3:02
add a comment |
Its weird: on Lambda, when I require the pool from the database.js file, it gives a reference to the same object. In local, it gives me a new pool object
– Jack Pilowsky
Nov 17 '18 at 11:08
Related topic: jeremydaly.com/reuse-database-connections-aws-lambda
– jarmod
Nov 19 '18 at 3:02
Its weird: on Lambda, when I require the pool from the database.js file, it gives a reference to the same object. In local, it gives me a new pool object
– Jack Pilowsky
Nov 17 '18 at 11:08
Its weird: on Lambda, when I require the pool from the database.js file, it gives a reference to the same object. In local, it gives me a new pool object
– Jack Pilowsky
Nov 17 '18 at 11:08
Related topic: jeremydaly.com/reuse-database-connections-aws-lambda
– jarmod
Nov 19 '18 at 3:02
Related topic: jeremydaly.com/reuse-database-connections-aws-lambda
– jarmod
Nov 19 '18 at 3:02
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53350316%2fdb-connection-management-in-aws-lambda-functions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53350316%2fdb-connection-management-in-aws-lambda-functions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Its weird: on Lambda, when I require the pool from the database.js file, it gives a reference to the same object. In local, it gives me a new pool object
– Jack Pilowsky
Nov 17 '18 at 11:08
Related topic: jeremydaly.com/reuse-database-connections-aws-lambda
– jarmod
Nov 19 '18 at 3:02