Multi-Thread Firebase function












0















So I am developing a Firebase function that accepts requests from users and updates few nodes under a branch these users are listening to.



My issue is if the function receives two client requests at the same time, that triggers two functions to execute and update the data at the same time.



I know this is typically solved by a transaction, but my updates are done on various nodes not only one value (i.e counter).



In a traditional multi-threading programming, this problems is solved by locking the code from executing so it can only be executed by one thread, where the next one resumes when the current one finishes.



Is this an option in Firebase Functions? If so, how can it be done?










share|improve this question



























    0















    So I am developing a Firebase function that accepts requests from users and updates few nodes under a branch these users are listening to.



    My issue is if the function receives two client requests at the same time, that triggers two functions to execute and update the data at the same time.



    I know this is typically solved by a transaction, but my updates are done on various nodes not only one value (i.e counter).



    In a traditional multi-threading programming, this problems is solved by locking the code from executing so it can only be executed by one thread, where the next one resumes when the current one finishes.



    Is this an option in Firebase Functions? If so, how can it be done?










    share|improve this question

























      0












      0








      0








      So I am developing a Firebase function that accepts requests from users and updates few nodes under a branch these users are listening to.



      My issue is if the function receives two client requests at the same time, that triggers two functions to execute and update the data at the same time.



      I know this is typically solved by a transaction, but my updates are done on various nodes not only one value (i.e counter).



      In a traditional multi-threading programming, this problems is solved by locking the code from executing so it can only be executed by one thread, where the next one resumes when the current one finishes.



      Is this an option in Firebase Functions? If so, how can it be done?










      share|improve this question














      So I am developing a Firebase function that accepts requests from users and updates few nodes under a branch these users are listening to.



      My issue is if the function receives two client requests at the same time, that triggers two functions to execute and update the data at the same time.



      I know this is typically solved by a transaction, but my updates are done on various nodes not only one value (i.e counter).



      In a traditional multi-threading programming, this problems is solved by locking the code from executing so it can only be executed by one thread, where the next one resumes when the current one finishes.



      Is this an option in Firebase Functions? If so, how can it be done?







      multithreading typescript firebase google-cloud-functions






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 31 '18 at 9:30









      masood elsadmasood elsad

      1911214




      1911214
























          1 Answer
          1






          active

          oldest

          votes


















          0














          There is currently no threading in Cloud Functions in any environment, both node and python included. You should not be depending on process level locking in Cloud Function - use a database transaction to ensure that updates are atomic and consistent. Each of your function invocations is going to be completely isolated from each other.






          share|improve this answer
























          • Thanks Doug, I think I need to rewrite the function and the structure so they don't conflict with each other that much.

            – masood elsad
            Dec 31 '18 at 10:19











          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%2f53985802%2fmulti-thread-firebase-function%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          There is currently no threading in Cloud Functions in any environment, both node and python included. You should not be depending on process level locking in Cloud Function - use a database transaction to ensure that updates are atomic and consistent. Each of your function invocations is going to be completely isolated from each other.






          share|improve this answer
























          • Thanks Doug, I think I need to rewrite the function and the structure so they don't conflict with each other that much.

            – masood elsad
            Dec 31 '18 at 10:19
















          0














          There is currently no threading in Cloud Functions in any environment, both node and python included. You should not be depending on process level locking in Cloud Function - use a database transaction to ensure that updates are atomic and consistent. Each of your function invocations is going to be completely isolated from each other.






          share|improve this answer
























          • Thanks Doug, I think I need to rewrite the function and the structure so they don't conflict with each other that much.

            – masood elsad
            Dec 31 '18 at 10:19














          0












          0








          0







          There is currently no threading in Cloud Functions in any environment, both node and python included. You should not be depending on process level locking in Cloud Function - use a database transaction to ensure that updates are atomic and consistent. Each of your function invocations is going to be completely isolated from each other.






          share|improve this answer













          There is currently no threading in Cloud Functions in any environment, both node and python included. You should not be depending on process level locking in Cloud Function - use a database transaction to ensure that updates are atomic and consistent. Each of your function invocations is going to be completely isolated from each other.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 31 '18 at 9:33









          Doug StevensonDoug Stevenson

          75.5k988108




          75.5k988108













          • Thanks Doug, I think I need to rewrite the function and the structure so they don't conflict with each other that much.

            – masood elsad
            Dec 31 '18 at 10:19



















          • Thanks Doug, I think I need to rewrite the function and the structure so they don't conflict with each other that much.

            – masood elsad
            Dec 31 '18 at 10:19

















          Thanks Doug, I think I need to rewrite the function and the structure so they don't conflict with each other that much.

          – masood elsad
          Dec 31 '18 at 10:19





          Thanks Doug, I think I need to rewrite the function and the structure so they don't conflict with each other that much.

          – masood elsad
          Dec 31 '18 at 10:19


















          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%2f53985802%2fmulti-thread-firebase-function%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

          Mossoró

          Error while reading .h5 file using the rhdf5 package in R

          Pushsharp Apns notification error: 'InvalidToken'