How to share cache between multiple Google App Engine instances which each have multiple vCPUs?











up vote
0
down vote

favorite












SITUATION:



I am trying to implement caching for rate-limited third-party API requests my website needs to make.



Apparently, basic solutions such as:



https://www.npmjs.com/package/node-cache



won't even share cache between CPUs, much less between instances ?



Is that correct ?



And if it is, how can I share cache between instances so that I have one unified cache for my website across instances ?



After googling for a while, it seems Redis would be a solution. But from what I gathered, I would have to host Redis on it's own dedicated instance for the cache to be unique across my website VM instances ?



What if the instance hosting Redis is overloaded and also needs to be auto-scaled to multiple instances ?




QUESTION:



How can I implement shared cache between VM instances of my website ?






javascript node.js google-app-engine caching redis







share|improve this question


























    up vote
    0
    down vote

    favorite












    SITUATION:



    I am trying to implement caching for rate-limited third-party API requests my website needs to make.



    Apparently, basic solutions such as:



    https://www.npmjs.com/package/node-cache



    won't even share cache between CPUs, much less between instances ?



    Is that correct ?



    And if it is, how can I share cache between instances so that I have one unified cache for my website across instances ?



    After googling for a while, it seems Redis would be a solution. But from what I gathered, I would have to host Redis on it's own dedicated instance for the cache to be unique across my website VM instances ?



    What if the instance hosting Redis is overloaded and also needs to be auto-scaled to multiple instances ?




    QUESTION:



    How can I implement shared cache between VM instances of my website ?






    javascript node.js google-app-engine caching redis







    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      SITUATION:



      I am trying to implement caching for rate-limited third-party API requests my website needs to make.



      Apparently, basic solutions such as:



      https://www.npmjs.com/package/node-cache



      won't even share cache between CPUs, much less between instances ?



      Is that correct ?



      And if it is, how can I share cache between instances so that I have one unified cache for my website across instances ?



      After googling for a while, it seems Redis would be a solution. But from what I gathered, I would have to host Redis on it's own dedicated instance for the cache to be unique across my website VM instances ?



      What if the instance hosting Redis is overloaded and also needs to be auto-scaled to multiple instances ?




      QUESTION:



      How can I implement shared cache between VM instances of my website ?






      javascript node.js google-app-engine caching redis







      share|improve this question













      SITUATION:



      I am trying to implement caching for rate-limited third-party API requests my website needs to make.



      Apparently, basic solutions such as:



      https://www.npmjs.com/package/node-cache



      won't even share cache between CPUs, much less between instances ?



      Is that correct ?



      And if it is, how can I share cache between instances so that I have one unified cache for my website across instances ?



      After googling for a while, it seems Redis would be a solution. But from what I gathered, I would have to host Redis on it's own dedicated instance for the cache to be unique across my website VM instances ?



      What if the instance hosting Redis is overloaded and also needs to be auto-scaled to multiple instances ?




      QUESTION:



      How can I implement shared cache between VM instances of my website ?






      javascript node.js google-app-engine caching redis




      javascript node.js google-app-engine caching redis






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 10 at 13:39









      TheProgrammer

      308117




      308117
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          You could add to your GAE application a 1st generation standard environment service which would:




          • act as a caching service for your node.js (or other 2nd generation standard environment or flexible environment) service(s) and, under the hood, use itself the GAE memcache service, only available in those 1st gen standard environments.

          • maybe even make itself those rate-limited 3rd party API calls, it will probably be simpler to properly coordinate the cached results that way

          • be configured for auto scaling to address the scalability concern






          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',
            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%2f53239542%2fhow-to-share-cache-between-multiple-google-app-engine-instances-which-each-have%23new-answer', 'question_page');
            }
            );

            Post as a guest


















            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote



            accepted










            You could add to your GAE application a 1st generation standard environment service which would:




            • act as a caching service for your node.js (or other 2nd generation standard environment or flexible environment) service(s) and, under the hood, use itself the GAE memcache service, only available in those 1st gen standard environments.

            • maybe even make itself those rate-limited 3rd party API calls, it will probably be simpler to properly coordinate the cached results that way

            • be configured for auto scaling to address the scalability concern






            share|improve this answer

























              up vote
              1
              down vote



              accepted










              You could add to your GAE application a 1st generation standard environment service which would:




              • act as a caching service for your node.js (or other 2nd generation standard environment or flexible environment) service(s) and, under the hood, use itself the GAE memcache service, only available in those 1st gen standard environments.

              • maybe even make itself those rate-limited 3rd party API calls, it will probably be simpler to properly coordinate the cached results that way

              • be configured for auto scaling to address the scalability concern






              share|improve this answer























                up vote
                1
                down vote



                accepted







                up vote
                1
                down vote



                accepted






                You could add to your GAE application a 1st generation standard environment service which would:




                • act as a caching service for your node.js (or other 2nd generation standard environment or flexible environment) service(s) and, under the hood, use itself the GAE memcache service, only available in those 1st gen standard environments.

                • maybe even make itself those rate-limited 3rd party API calls, it will probably be simpler to properly coordinate the cached results that way

                • be configured for auto scaling to address the scalability concern






                share|improve this answer












                You could add to your GAE application a 1st generation standard environment service which would:




                • act as a caching service for your node.js (or other 2nd generation standard environment or flexible environment) service(s) and, under the hood, use itself the GAE memcache service, only available in those 1st gen standard environments.

                • maybe even make itself those rate-limited 3rd party API calls, it will probably be simpler to properly coordinate the cached results that way

                • be configured for auto scaling to address the scalability concern







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 10 at 21:29









                Dan Cornilescu

                26.3k113160




                26.3k113160






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239542%2fhow-to-share-cache-between-multiple-google-app-engine-instances-which-each-have%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest






































































                    -

                    Popular posts from this blog

                    Florida Star v. B. J. F.

                    Image
                    Florida Star v. B. J. F. From Wikipedia, the free encyclopedia Jump to navigation Jump to search United States Supreme Court case Florida Star v. B. J. F. Supreme Court of the United States Argued March 21, 1989 Decided June 21, 1989 Full case name The Florida Star v. B. J. F. Citations 491 U.S. 524 ( more ) 109 S. Ct. 2603; 105 L. Ed. 2d 443; 1989 U.S. LEXIS 3120; 57 U.S.L.W. 4816; 16 Media L. Rep. 1801 Prior history The Florida Star v. B.J.F., 530 So.2d 286 (1988) Supreme Court of Florida; Florida Star v. B.J.F., 499 So.2d 883 (1986) Fla. Dist. Court of Appeals Holding Florida Stat. § 794.03 is unconstitutional to the extent it makes the truthful reporting of information that was a matter of public record unlawful, as it violates the First Amendment. Court membership Chief Justice William Rehnquist Associate Justices William J. Brennan Jr.  · Byron White Thurgood Marshall  · Harry Blac
                    Read more

                    Danny Elfman

                    Image
                    Danny Elfman From Wikipedia, the free encyclopedia Jump to navigation Jump to search Danny Elfman Elfman at the 2010 San Diego Comic-Con Born Daniel Robert Elfman ( 1953-05-29 ) May 29, 1953 (age 65) Los Angeles, California, U.S. Spouse(s) Bridget Fonda ( m.  2003) Children 1 Musical career Genres Rock [1] ska [2] new wave film music video game music Occupation(s) Composer, singer, songwriter, record producer Instruments Trombone guitar percussion vocals keyboards [3] Years active 1972–present Associated acts Oingo Boingo James Newton Howard Daniel Robert Elfman (born May 29, 1953) is an American composer, singer, songwriter, and record producer. Elfman first became known for being the lead singer and songwriter for the band Oingo Boingo from 1974 to 1995. He is well known for scoring films and television shows, particularly his frequent collabora
                    Read more

                    Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues

                    Image
                    .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I am trying to use the TumblR package in R to set up the Oauth Authentication to Retrieve a user's dashboard using the second example in tumblR documentation However I get the following error, it seems that using twitter others have been able to use a different function to get around this, but I am not finding the same function available for Tumblr. See twitter package for R authentication: error 401 My code consumer_key <- OKey consumer_secret <- SKey appname <- App_name tokenURL <- 'http://www.tumblr.com/oauth/request_token' accessTokenURL <- 'http://www.tumblr.com/oauth/acces_token'
                    Read more