How to scale restful api with load balancing while keeping quota limits
up vote
0
down vote
favorite
So I want to offer an API as as service, you pay x/month for 1000 queries per day as an example. If I have a master database, with two replicas, and multiple api servers, how do I make sure that a customer gets 1000 queries per day and no more? Would sticky sessions based on a header containing their api key be the best option?
Every query needs to be logged, eventually making it to every database. And the total quota of the day usage needs to be accurate.
api load-balancing quota
asked Nov 9 at 23:27
Rabbit G
204
add a comment |
up vote
0
down vote
favorite
So I want to offer an API as as service, you pay x/month for 1000 queries per day as an example. If I have a master database, with two replicas, and multiple api servers, how do I make sure that a customer gets 1000 queries per day and no more? Would sticky sessions based on a header containing their api key be the best option?
Every query needs to be logged, eventually making it to every database. And the total quota of the day usage needs to be accurate.
api load-balancing quota
asked Nov 9 at 23:27
Rabbit G
204
In every authenticated call along with the query to the db you send also an update to the profile of the user increasing the daily counter. Every night a procedure will reset all the users counters. No need for sticky sessions.
– zochamx
Nov 11 at 20:51
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
So I want to offer an API as as service, you pay x/month for 1000 queries per day as an example. If I have a master database, with two replicas, and multiple api servers, how do I make sure that a customer gets 1000 queries per day and no more? Would sticky sessions based on a header containing their api key be the best option?
Every query needs to be logged, eventually making it to every database. And the total quota of the day usage needs to be accurate.
api load-balancing quota
asked Nov 9 at 23:27
Rabbit G
204
So I want to offer an API as as service, you pay x/month for 1000 queries per day as an example. If I have a master database, with two replicas, and multiple api servers, how do I make sure that a customer gets 1000 queries per day and no more? Would sticky sessions based on a header containing their api key be the best option?
Every query needs to be logged, eventually making it to every database. And the total quota of the day usage needs to be accurate.
api load-balancing quota
api load-balancing quota
asked Nov 9 at 23:27
Rabbit G
204
asked Nov 9 at 23:27
Rabbit G
204
asked Nov 9 at 23:27
Rabbit G
204
asked Nov 9 at 23:27
Rabbit G
204
asked Nov 9 at 23:27
Rabbit G
204
204
In every authenticated call along with the query to the db you send also an update to the profile of the user increasing the daily counter. Every night a procedure will reset all the users counters. No need for sticky sessions.
– zochamx
Nov 11 at 20:51
add a comment |
In every authenticated call along with the query to the db you send also an update to the profile of the user increasing the daily counter. Every night a procedure will reset all the users counters. No need for sticky sessions.
– zochamx
Nov 11 at 20:51
In every authenticated call along with the query to the db you send also an update to the profile of the user increasing the daily counter. Every night a procedure will reset all the users counters. No need for sticky sessions.
– zochamx
Nov 11 at 20:51
In every authenticated call along with the query to the db you send also an update to the profile of the user increasing the daily counter. Every night a procedure will reset all the users counters. No need for sticky sessions.
– zochamx
Nov 11 at 20:51
add a comment |
active
oldest
votes
active
oldest
votes
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%2f53234537%2fhow-to-scale-restful-api-with-load-balancing-while-keeping-quota-limits%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
In every authenticated call along with the query to the db you send also an update to the profile of the user increasing the daily counter. Every night a procedure will reset all the users counters. No need for sticky sessions.
– zochamx
Nov 11 at 20:51