Should the state of a multi-container docker application be persisted by using non-binary files identified by...
I am currently researching best practices to persist data and make it efficiently available in a multi-container docker application.
Most docker applications use databases to persist data but it makes your application dependent on the database-engines version so if a new feature is needed migrations have to take place.
Migrations take a lot of time to plan, slow development, are prone to errors and could (worst case) leave the state completely broken.
To bypass this problem I have often asked myself why not just create a volume and read/write all data from/to a volume in a UUID/SESSION-ID.JSON manner?
This way each container stays stateless/ephemeral and can read the state from the volume at any time which makes it easily scalable and since there can only be one UUID/SESSION-ID the problem of simultaneous writes gets resolved implicitly.
What would be the problem with such an application-architecture?
docker architecture docker-volume stateless stateless-session
asked Nov 19 '18 at 9:23
ThodiThodi
148113
add a comment |
I am currently researching best practices to persist data and make it efficiently available in a multi-container docker application.
Most docker applications use databases to persist data but it makes your application dependent on the database-engines version so if a new feature is needed migrations have to take place.
Migrations take a lot of time to plan, slow development, are prone to errors and could (worst case) leave the state completely broken.
To bypass this problem I have often asked myself why not just create a volume and read/write all data from/to a volume in a UUID/SESSION-ID.JSON manner?
This way each container stays stateless/ephemeral and can read the state from the volume at any time which makes it easily scalable and since there can only be one UUID/SESSION-ID the problem of simultaneous writes gets resolved implicitly.
What would be the problem with such an application-architecture?
docker architecture docker-volume stateless stateless-session
asked Nov 19 '18 at 9:23
ThodiThodi
148113
add a comment |
I am currently researching best practices to persist data and make it efficiently available in a multi-container docker application.
Most docker applications use databases to persist data but it makes your application dependent on the database-engines version so if a new feature is needed migrations have to take place.
Migrations take a lot of time to plan, slow development, are prone to errors and could (worst case) leave the state completely broken.
To bypass this problem I have often asked myself why not just create a volume and read/write all data from/to a volume in a UUID/SESSION-ID.JSON manner?
This way each container stays stateless/ephemeral and can read the state from the volume at any time which makes it easily scalable and since there can only be one UUID/SESSION-ID the problem of simultaneous writes gets resolved implicitly.
What would be the problem with such an application-architecture?
docker architecture docker-volume stateless stateless-session
asked Nov 19 '18 at 9:23
ThodiThodi
148113
I am currently researching best practices to persist data and make it efficiently available in a multi-container docker application.
Most docker applications use databases to persist data but it makes your application dependent on the database-engines version so if a new feature is needed migrations have to take place.
Migrations take a lot of time to plan, slow development, are prone to errors and could (worst case) leave the state completely broken.
To bypass this problem I have often asked myself why not just create a volume and read/write all data from/to a volume in a UUID/SESSION-ID.JSON manner?
This way each container stays stateless/ephemeral and can read the state from the volume at any time which makes it easily scalable and since there can only be one UUID/SESSION-ID the problem of simultaneous writes gets resolved implicitly.
What would be the problem with such an application-architecture?
docker architecture docker-volume stateless stateless-session
docker architecture docker-volume stateless stateless-session
asked Nov 19 '18 at 9:23
ThodiThodi
148113
asked Nov 19 '18 at 9:23
ThodiThodi
148113
edited Nov 19 '18 at 12:47
Thodi
asked Nov 19 '18 at 9:23
ThodiThodi
148113
asked Nov 19 '18 at 9:23
ThodiThodi
148113
asked Nov 19 '18 at 9:23
ThodiThodi
148113
148113
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%2f53371570%2fshould-the-state-of-a-multi-container-docker-application-be-persisted-by-using-n%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%2f53371570%2fshould-the-state-of-a-multi-container-docker-application-be-persisted-by-using-n%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
