Phalcon data to elastic search via beanstalkd












0















Which would be efficient in terms of speed and resources?
Scenario 1
Write all data to a table where in each field represents ElasticSearch index?
Execute a cron or event to write data to ES index based on table data.
Scenario 2
Write all data to beanstalkd queue and fire an event to write job queue data to Elastic Search.










share|improve this question



























    0















    Which would be efficient in terms of speed and resources?
    Scenario 1
    Write all data to a table where in each field represents ElasticSearch index?
    Execute a cron or event to write data to ES index based on table data.
    Scenario 2
    Write all data to beanstalkd queue and fire an event to write job queue data to Elastic Search.










    share|improve this question

























      0












      0








      0








      Which would be efficient in terms of speed and resources?
      Scenario 1
      Write all data to a table where in each field represents ElasticSearch index?
      Execute a cron or event to write data to ES index based on table data.
      Scenario 2
      Write all data to beanstalkd queue and fire an event to write job queue data to Elastic Search.










      share|improve this question














      Which would be efficient in terms of speed and resources?
      Scenario 1
      Write all data to a table where in each field represents ElasticSearch index?
      Execute a cron or event to write data to ES index based on table data.
      Scenario 2
      Write all data to beanstalkd queue and fire an event to write job queue data to Elastic Search.







      elasticsearch phalcon beanstalkd






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 11:36









      AGCODERAGCODER

      14




      14
























          2 Answers
          2






          active

          oldest

          votes


















          0














          I would say scenario 2 is your best choice and the one I've already done in the past, my only question would be, why not save it directly to elastic or is it to slow for you?






          share|improve this answer































            0














            the 2nd scenario is better, because it can help you to optimize resources of your servers
            With the cronjob, you need scan your table everytime to find new data => not good for the performance
            Hope it can help you






            share|improve this answer























              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%2f53373810%2fphalcon-data-to-elastic-search-via-beanstalkd%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              I would say scenario 2 is your best choice and the one I've already done in the past, my only question would be, why not save it directly to elastic or is it to slow for you?






              share|improve this answer




























                0














                I would say scenario 2 is your best choice and the one I've already done in the past, my only question would be, why not save it directly to elastic or is it to slow for you?






                share|improve this answer


























                  0












                  0








                  0







                  I would say scenario 2 is your best choice and the one I've already done in the past, my only question would be, why not save it directly to elastic or is it to slow for you?






                  share|improve this answer













                  I would say scenario 2 is your best choice and the one I've already done in the past, my only question would be, why not save it directly to elastic or is it to slow for you?







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 23 '18 at 22:16









                  Max CastroMax Castro

                  1




                  1

























                      0














                      the 2nd scenario is better, because it can help you to optimize resources of your servers
                      With the cronjob, you need scan your table everytime to find new data => not good for the performance
                      Hope it can help you






                      share|improve this answer




























                        0














                        the 2nd scenario is better, because it can help you to optimize resources of your servers
                        With the cronjob, you need scan your table everytime to find new data => not good for the performance
                        Hope it can help you






                        share|improve this answer


























                          0












                          0








                          0







                          the 2nd scenario is better, because it can help you to optimize resources of your servers
                          With the cronjob, you need scan your table everytime to find new data => not good for the performance
                          Hope it can help you






                          share|improve this answer













                          the 2nd scenario is better, because it can help you to optimize resources of your servers
                          With the cronjob, you need scan your table everytime to find new data => not good for the performance
                          Hope it can help you







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Dec 11 '18 at 12:13









                          NGUYEN Phuc ThinhNGUYEN Phuc Thinh

                          11




                          11






























                              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%2f53373810%2fphalcon-data-to-elastic-search-via-beanstalkd%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







                              這個網誌中的熱門文章

                              Xamarin.form Move up view when keyboard appear

                              Post-Redirect-Get with Spring WebFlux and Thymeleaf

                              Anylogic : not able to use stopDelay()