Scaling of microservice to handle more request
I am using couchbase as a DB for my Sprint boot microservice. To handle more request/sec I want to create more instances of my service. How can we handle this design to make the DB consistent? As of now, I have a single couchbase running and 4 instances of my service.
I am thinking of future problem by running more instances.As all request are creating data (posting) data to CB.
microservices couchbase scaling
add a comment |
I am using couchbase as a DB for my Sprint boot microservice. To handle more request/sec I want to create more instances of my service. How can we handle this design to make the DB consistent? As of now, I have a single couchbase running and 4 instances of my service.
I am thinking of future problem by running more instances.As all request are creating data (posting) data to CB.
microservices couchbase scaling
add a comment |
I am using couchbase as a DB for my Sprint boot microservice. To handle more request/sec I want to create more instances of my service. How can we handle this design to make the DB consistent? As of now, I have a single couchbase running and 4 instances of my service.
I am thinking of future problem by running more instances.As all request are creating data (posting) data to CB.
microservices couchbase scaling
I am using couchbase as a DB for my Sprint boot microservice. To handle more request/sec I want to create more instances of my service. How can we handle this design to make the DB consistent? As of now, I have a single couchbase running and 4 instances of my service.
I am thinking of future problem by running more instances.As all request are creating data (posting) data to CB.
microservices couchbase scaling
microservices couchbase scaling
asked Dec 31 '18 at 3:45
dead programmerdead programmer
1,77762752
1,77762752
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If your single server is maxed out, you need to add more servers. The docs explain how to do that.
https://docs.couchbase.com/server/6.0/manage/manage-nodes/add-node-and-rebalance.html
If your consistency concerns are fairly simple, CAS values may solve your problem.
https://docs.couchbase.com/java-sdk/2.7/document-operations.html
If you have more detailed concerns about consistency, you need to explain what they are in your question. Generally speaking, if consistency is a priority, a NoSQL database like Couchbase is probably not the right tool for you.
While it's true Couchbase is not a silver bullet, it's worth noting that reads and writes via the Couchbase key/value API are indeed strongly consistent (in the sense that everyone else can immediately read your writes). It's even possible to do consistent reads via the Query service using scan consistency options (although that's a bit more expensive than the normal eventually-consistent queries).
– dnault
Jan 4 at 3:41
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%2f53983400%2fscaling-of-microservice-to-handle-more-request%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
If your single server is maxed out, you need to add more servers. The docs explain how to do that.
https://docs.couchbase.com/server/6.0/manage/manage-nodes/add-node-and-rebalance.html
If your consistency concerns are fairly simple, CAS values may solve your problem.
https://docs.couchbase.com/java-sdk/2.7/document-operations.html
If you have more detailed concerns about consistency, you need to explain what they are in your question. Generally speaking, if consistency is a priority, a NoSQL database like Couchbase is probably not the right tool for you.
While it's true Couchbase is not a silver bullet, it's worth noting that reads and writes via the Couchbase key/value API are indeed strongly consistent (in the sense that everyone else can immediately read your writes). It's even possible to do consistent reads via the Query service using scan consistency options (although that's a bit more expensive than the normal eventually-consistent queries).
– dnault
Jan 4 at 3:41
add a comment |
If your single server is maxed out, you need to add more servers. The docs explain how to do that.
https://docs.couchbase.com/server/6.0/manage/manage-nodes/add-node-and-rebalance.html
If your consistency concerns are fairly simple, CAS values may solve your problem.
https://docs.couchbase.com/java-sdk/2.7/document-operations.html
If you have more detailed concerns about consistency, you need to explain what they are in your question. Generally speaking, if consistency is a priority, a NoSQL database like Couchbase is probably not the right tool for you.
While it's true Couchbase is not a silver bullet, it's worth noting that reads and writes via the Couchbase key/value API are indeed strongly consistent (in the sense that everyone else can immediately read your writes). It's even possible to do consistent reads via the Query service using scan consistency options (although that's a bit more expensive than the normal eventually-consistent queries).
– dnault
Jan 4 at 3:41
add a comment |
If your single server is maxed out, you need to add more servers. The docs explain how to do that.
https://docs.couchbase.com/server/6.0/manage/manage-nodes/add-node-and-rebalance.html
If your consistency concerns are fairly simple, CAS values may solve your problem.
https://docs.couchbase.com/java-sdk/2.7/document-operations.html
If you have more detailed concerns about consistency, you need to explain what they are in your question. Generally speaking, if consistency is a priority, a NoSQL database like Couchbase is probably not the right tool for you.
If your single server is maxed out, you need to add more servers. The docs explain how to do that.
https://docs.couchbase.com/server/6.0/manage/manage-nodes/add-node-and-rebalance.html
If your consistency concerns are fairly simple, CAS values may solve your problem.
https://docs.couchbase.com/java-sdk/2.7/document-operations.html
If you have more detailed concerns about consistency, you need to explain what they are in your question. Generally speaking, if consistency is a priority, a NoSQL database like Couchbase is probably not the right tool for you.
answered Dec 31 '18 at 12:44
Johan LarsonJohan Larson
1,1461712
1,1461712
While it's true Couchbase is not a silver bullet, it's worth noting that reads and writes via the Couchbase key/value API are indeed strongly consistent (in the sense that everyone else can immediately read your writes). It's even possible to do consistent reads via the Query service using scan consistency options (although that's a bit more expensive than the normal eventually-consistent queries).
– dnault
Jan 4 at 3:41
add a comment |
While it's true Couchbase is not a silver bullet, it's worth noting that reads and writes via the Couchbase key/value API are indeed strongly consistent (in the sense that everyone else can immediately read your writes). It's even possible to do consistent reads via the Query service using scan consistency options (although that's a bit more expensive than the normal eventually-consistent queries).
– dnault
Jan 4 at 3:41
While it's true Couchbase is not a silver bullet, it's worth noting that reads and writes via the Couchbase key/value API are indeed strongly consistent (in the sense that everyone else can immediately read your writes). It's even possible to do consistent reads via the Query service using scan consistency options (although that's a bit more expensive than the normal eventually-consistent queries).
– dnault
Jan 4 at 3:41
While it's true Couchbase is not a silver bullet, it's worth noting that reads and writes via the Couchbase key/value API are indeed strongly consistent (in the sense that everyone else can immediately read your writes). It's even possible to do consistent reads via the Query service using scan consistency options (although that's a bit more expensive than the normal eventually-consistent queries).
– dnault
Jan 4 at 3:41
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%2f53983400%2fscaling-of-microservice-to-handle-more-request%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