Handle Critical Session outside code - Java
In my project, multiple race condition scenarios are taken care by writing critical section inside the code as there is no locking mechanism available for Blazegraph database. Application is deployed in AWS Fargate(docker).
Disadvantage is that we are not able to scale the application in multiple containers due to synchronized block in the code.
Example:
- I have a project with multiple revisions. Only one user should be able to commit at a time. Commit is done by reading latest revision number in the project. Hence code to fetch latest revision number and commit new revision is in a synchronized block.
- An object counter is maintained in project in order to generate sequential id for every save request. Hence code to fetch latest object counter and increment is in a synchronized block
Possible options:
- maintain queue - too costly as all the requests need to be routed via queue
- keep "uuid" as id - business reasons. cannot be changed
Any suggestions are welcome. Thank you so much in advance.
docker java-ee critical-section aws-fargate blazegraph
add a comment |
In my project, multiple race condition scenarios are taken care by writing critical section inside the code as there is no locking mechanism available for Blazegraph database. Application is deployed in AWS Fargate(docker).
Disadvantage is that we are not able to scale the application in multiple containers due to synchronized block in the code.
Example:
- I have a project with multiple revisions. Only one user should be able to commit at a time. Commit is done by reading latest revision number in the project. Hence code to fetch latest revision number and commit new revision is in a synchronized block.
- An object counter is maintained in project in order to generate sequential id for every save request. Hence code to fetch latest object counter and increment is in a synchronized block
Possible options:
- maintain queue - too costly as all the requests need to be routed via queue
- keep "uuid" as id - business reasons. cannot be changed
Any suggestions are welcome. Thank you so much in advance.
docker java-ee critical-section aws-fargate blazegraph
add a comment |
In my project, multiple race condition scenarios are taken care by writing critical section inside the code as there is no locking mechanism available for Blazegraph database. Application is deployed in AWS Fargate(docker).
Disadvantage is that we are not able to scale the application in multiple containers due to synchronized block in the code.
Example:
- I have a project with multiple revisions. Only one user should be able to commit at a time. Commit is done by reading latest revision number in the project. Hence code to fetch latest revision number and commit new revision is in a synchronized block.
- An object counter is maintained in project in order to generate sequential id for every save request. Hence code to fetch latest object counter and increment is in a synchronized block
Possible options:
- maintain queue - too costly as all the requests need to be routed via queue
- keep "uuid" as id - business reasons. cannot be changed
Any suggestions are welcome. Thank you so much in advance.
docker java-ee critical-section aws-fargate blazegraph
In my project, multiple race condition scenarios are taken care by writing critical section inside the code as there is no locking mechanism available for Blazegraph database. Application is deployed in AWS Fargate(docker).
Disadvantage is that we are not able to scale the application in multiple containers due to synchronized block in the code.
Example:
- I have a project with multiple revisions. Only one user should be able to commit at a time. Commit is done by reading latest revision number in the project. Hence code to fetch latest revision number and commit new revision is in a synchronized block.
- An object counter is maintained in project in order to generate sequential id for every save request. Hence code to fetch latest object counter and increment is in a synchronized block
Possible options:
- maintain queue - too costly as all the requests need to be routed via queue
- keep "uuid" as id - business reasons. cannot be changed
Any suggestions are welcome. Thank you so much in advance.
docker java-ee critical-section aws-fargate blazegraph
docker java-ee critical-section aws-fargate blazegraph
edited Nov 22 '18 at 13:09


Wolfgang Fahl
6,65564498
6,65564498
asked Oct 30 '18 at 9:52
LinzLinz
1098
1098
add a comment |
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%2f53061556%2fhandle-critical-session-outside-code-java%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.
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%2f53061556%2fhandle-critical-session-outside-code-java%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