Should the state of a multi-container docker application be persisted by read/writing...











up vote
0
down vote

favorite












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







share|improve this question


























    up vote
    0
    down vote

    favorite












    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







    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      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







      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 1 hour ago









      Thodi

      12312




      12312





























          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',
          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
          });


          }
          });














           

          draft saved


          draft discarded


















          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-read-wr%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          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-read-wr%23new-answer', 'question_page');
          }
          );

          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







          Popular posts from this blog

          MongoDB - Not Authorized To Execute Command

          Image
          .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I have successfully enabled authorization on MongoDB and I have created an account on the admin database and then I created an account for my database called test. The following connection string to connect to my test database works successfully: mongo --host 192.168.17.52 --port 27017 -u user1 -p password --authenticationDatabase test Only problem I have now is, I cannot execute commands such as: show dbs. I get the following error when I try to do so: "errmsg" : "not authorized on admin to execute command { listDatabases: 1.0, lsid: { id: UUID("a1d5bc0d-bc58-485e-b232-270758a89455") }, $db: "admin...
          Read more

          Npm cannot find a required file even through it is in the searched directory

          Image
          up vote 0 down vote favorite I got that error: users-Air:pdfuploader user$ npm run start client@0.1.0 start /Users/user/Documents/pdfuploader react-scripts start Could not find a required file. Name: index.html Searched in: /Users/user/Documents/pdfuploader/public npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! client@0.1.0 start: `react-scripts start` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the client@0.1.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /Users/user/.npm/_logs/2018-11-19T10_19_14_555Z-debug.log users-Air:pdfuploader user$ And the file is in /Users/user/Documents/pdfuploader/public as you can see in my github repository: https://github.c...
          Read more

          in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

          Image
          1 I tried to upgrade a yummy sandwich made of two test slices (@JsonTest and @JdbcTest in my case, crunchy test code in between) adding spring boot 2.1 flavour to it. But it seems it was not much of a success. I cannot annotate my tests with many @...Test since they are now each bringing their own XxxTestContextBootstrapper. It used to work when they all used same SpringBootTestContextBootstrapper. @RunWith(SpringRunner.class) @JdbcTest @JsonTest public class Test { @Test public void test() { System.out.printn("Hello, World !"); } } The error I get from BootstrapUtils is illegalStateException : Configuration error: found multiple declarations of @BootstrapWith for test class I understand I might be doing something wrong here but is there an easy way I could load both Json and Jdbc contex...
          Read more