Make post calls on hold
I have a Node.js application and I deployed it on Heroku. The API calls are made from a native app. I am using Postgresql for database (Sequelize as orm) and my db allows maximum 20 connections.
When those connections are full I get an error message "too many connections for role ..." and if there's a post request made at that moment it's not saved.
Is there a way to put the request "on hold" and to complete it as soon as the connection is available?
node.js heroku sequelize.js
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
add a comment |
I have a Node.js application and I deployed it on Heroku. The API calls are made from a native app. I am using Postgresql for database (Sequelize as orm) and my db allows maximum 20 connections.
When those connections are full I get an error message "too many connections for role ..." and if there's a post request made at that moment it's not saved.
Is there a way to put the request "on hold" and to complete it as soon as the connection is available?
node.js heroku sequelize.js
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
add a comment |
I have a Node.js application and I deployed it on Heroku. The API calls are made from a native app. I am using Postgresql for database (Sequelize as orm) and my db allows maximum 20 connections.
When those connections are full I get an error message "too many connections for role ..." and if there's a post request made at that moment it's not saved.
Is there a way to put the request "on hold" and to complete it as soon as the connection is available?
node.js heroku sequelize.js
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
I have a Node.js application and I deployed it on Heroku. The API calls are made from a native app. I am using Postgresql for database (Sequelize as orm) and my db allows maximum 20 connections.
When those connections are full I get an error message "too many connections for role ..." and if there's a post request made at that moment it's not saved.
Is there a way to put the request "on hold" and to complete it as soon as the connection is available?
node.js heroku sequelize.js
node.js heroku sequelize.js
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
asked Nov 14 '18 at 4:25
Tom BombTom Bomb
389213
389213
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There's nothing built into the platform that will allow you to arbitrarily queue requests based on conditions at the application level. Instead of dropping these requests outright you could implement a connection pool with Sequelize (docs here and here) which should improve the user experience by limiting the number of connections consumed by the app. This way your application will hold onto those requests for a short while (likely until the platform times them out) but it will at least give your app a chance to process them.
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
add a comment |
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%2f53293176%2fmake-post-calls-on-hold%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There's nothing built into the platform that will allow you to arbitrarily queue requests based on conditions at the application level. Instead of dropping these requests outright you could implement a connection pool with Sequelize (docs here and here) which should improve the user experience by limiting the number of connections consumed by the app. This way your application will hold onto those requests for a short while (likely until the platform times them out) but it will at least give your app a chance to process them.
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
add a comment |
There's nothing built into the platform that will allow you to arbitrarily queue requests based on conditions at the application level. Instead of dropping these requests outright you could implement a connection pool with Sequelize (docs here and here) which should improve the user experience by limiting the number of connections consumed by the app. This way your application will hold onto those requests for a short while (likely until the platform times them out) but it will at least give your app a chance to process them.
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
add a comment |
There's nothing built into the platform that will allow you to arbitrarily queue requests based on conditions at the application level. Instead of dropping these requests outright you could implement a connection pool with Sequelize (docs here and here) which should improve the user experience by limiting the number of connections consumed by the app. This way your application will hold onto those requests for a short while (likely until the platform times them out) but it will at least give your app a chance to process them.
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
There's nothing built into the platform that will allow you to arbitrarily queue requests based on conditions at the application level. Instead of dropping these requests outright you could implement a connection pool with Sequelize (docs here and here) which should improve the user experience by limiting the number of connections consumed by the app. This way your application will hold onto those requests for a short while (likely until the platform times them out) but it will at least give your app a chance to process them.
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
answered Nov 14 '18 at 4:41
RangerRangerRangerRanger
1,1842925
1,1842925
add a comment |
add a comment |
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.
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%2f53293176%2fmake-post-calls-on-hold%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
