User Timeline's & Data Replication in Cassandra










0















I am currently creating the backend for an instagram clone and using Cassandra as the database (first time NoSQL). I have tried to denormalize my data - but it just doesn't feel right. The replication level is N (where N is the number of followers / subscribers).



I am aware of how the primary key is composed of two parts (partition key & clustering columns) and tried to model accordingly.



 CREATE TABLE IF NOT EXISTS instagram.user_post (
user_id uuid,
post_id timeuuid,
tag text,
caption text,
PRIMARY KEY (user_id, post_id)
) WITH CLUSTERING ORDER BY (post_id DESC);

CREATE TABLE IF NOT EXISTS instagram.user_post_comment (
user_id uuid,
post_id timeuuid,
comment text,
PRIMARY KEY (user_id, post_id)
) WITH CLUSTERING ORDER BY (post_id DESC);


CREATE TABLE IF NOT EXISTS instagram.user_post_timeline (
user_id uuid,
post_id timeuuid,
caption text,
month text,
PRIMARY KEY ((user_id, month) post_id)
) WITH CLUSTERING ORDER BY (post_id DESC);


If "Joe" makes a post and has 400 followers, my code would create 400 instagram.user_post_timeline entries....one for each user. I keep on reading data duplication is ok - but this just seems extreme. Is there a better way to do this? (I am aware twitter keeps ZIPLISTS in redis for each user ...but thats just a cache).



Thanks










share|improve this question


























    0















    I am currently creating the backend for an instagram clone and using Cassandra as the database (first time NoSQL). I have tried to denormalize my data - but it just doesn't feel right. The replication level is N (where N is the number of followers / subscribers).



    I am aware of how the primary key is composed of two parts (partition key & clustering columns) and tried to model accordingly.



     CREATE TABLE IF NOT EXISTS instagram.user_post (
    user_id uuid,
    post_id timeuuid,
    tag text,
    caption text,
    PRIMARY KEY (user_id, post_id)
    ) WITH CLUSTERING ORDER BY (post_id DESC);

    CREATE TABLE IF NOT EXISTS instagram.user_post_comment (
    user_id uuid,
    post_id timeuuid,
    comment text,
    PRIMARY KEY (user_id, post_id)
    ) WITH CLUSTERING ORDER BY (post_id DESC);


    CREATE TABLE IF NOT EXISTS instagram.user_post_timeline (
    user_id uuid,
    post_id timeuuid,
    caption text,
    month text,
    PRIMARY KEY ((user_id, month) post_id)
    ) WITH CLUSTERING ORDER BY (post_id DESC);


    If "Joe" makes a post and has 400 followers, my code would create 400 instagram.user_post_timeline entries....one for each user. I keep on reading data duplication is ok - but this just seems extreme. Is there a better way to do this? (I am aware twitter keeps ZIPLISTS in redis for each user ...but thats just a cache).



    Thanks










    share|improve this question
























      0












      0








      0








      I am currently creating the backend for an instagram clone and using Cassandra as the database (first time NoSQL). I have tried to denormalize my data - but it just doesn't feel right. The replication level is N (where N is the number of followers / subscribers).



      I am aware of how the primary key is composed of two parts (partition key & clustering columns) and tried to model accordingly.



       CREATE TABLE IF NOT EXISTS instagram.user_post (
      user_id uuid,
      post_id timeuuid,
      tag text,
      caption text,
      PRIMARY KEY (user_id, post_id)
      ) WITH CLUSTERING ORDER BY (post_id DESC);

      CREATE TABLE IF NOT EXISTS instagram.user_post_comment (
      user_id uuid,
      post_id timeuuid,
      comment text,
      PRIMARY KEY (user_id, post_id)
      ) WITH CLUSTERING ORDER BY (post_id DESC);


      CREATE TABLE IF NOT EXISTS instagram.user_post_timeline (
      user_id uuid,
      post_id timeuuid,
      caption text,
      month text,
      PRIMARY KEY ((user_id, month) post_id)
      ) WITH CLUSTERING ORDER BY (post_id DESC);


      If "Joe" makes a post and has 400 followers, my code would create 400 instagram.user_post_timeline entries....one for each user. I keep on reading data duplication is ok - but this just seems extreme. Is there a better way to do this? (I am aware twitter keeps ZIPLISTS in redis for each user ...but thats just a cache).



      Thanks










      share|improve this question














      I am currently creating the backend for an instagram clone and using Cassandra as the database (first time NoSQL). I have tried to denormalize my data - but it just doesn't feel right. The replication level is N (where N is the number of followers / subscribers).



      I am aware of how the primary key is composed of two parts (partition key & clustering columns) and tried to model accordingly.



       CREATE TABLE IF NOT EXISTS instagram.user_post (
      user_id uuid,
      post_id timeuuid,
      tag text,
      caption text,
      PRIMARY KEY (user_id, post_id)
      ) WITH CLUSTERING ORDER BY (post_id DESC);

      CREATE TABLE IF NOT EXISTS instagram.user_post_comment (
      user_id uuid,
      post_id timeuuid,
      comment text,
      PRIMARY KEY (user_id, post_id)
      ) WITH CLUSTERING ORDER BY (post_id DESC);


      CREATE TABLE IF NOT EXISTS instagram.user_post_timeline (
      user_id uuid,
      post_id timeuuid,
      caption text,
      month text,
      PRIMARY KEY ((user_id, month) post_id)
      ) WITH CLUSTERING ORDER BY (post_id DESC);


      If "Joe" makes a post and has 400 followers, my code would create 400 instagram.user_post_timeline entries....one for each user. I keep on reading data duplication is ok - but this just seems extreme. Is there a better way to do this? (I am aware twitter keeps ZIPLISTS in redis for each user ...but thats just a cache).



      Thanks







      cassandra






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 14 '18 at 22:15









      NateNate

      134




      134






















          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
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309555%2fuser-timelines-data-replication-in-cassandra%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















          draft saved

          draft discarded
















































          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309555%2fuser-timelines-data-replication-in-cassandra%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

          Top Tejano songwriter Luis Silva dead of heart attack at 64

          政党

          天津地下鉄3号線