Azure API Management Poor Man's Multi Region using Basic/Standard plans











up vote
0
down vote

favorite












We have an application built of multiple Logic Apps. We will use Azure API Management to consolidate all those endpoints into a single endpoint.



We need this application to be highly available, so we want to deploy it to 2 regions (eg West Europe and North Europe).



As of Nov 2018, the only API Management plan that supports multi-region is the Premium plan that costs 18x the Basic plan. The Premium plan is way out of our budget.



We had the idea to setup two Basic API Management units, one for each region, having both configurations synchronized, and placing a Traffic Manager in front of both.



Assuming that we will only use the gateway functionality of API Management (not developer/publisher portal, authentication etc), what will we be missing with our "Poor Man's Multi Region" solution instead of going with the "native" multi-region of the Premium plan?










share|improve this question


























    up vote
    0
    down vote

    favorite












    We have an application built of multiple Logic Apps. We will use Azure API Management to consolidate all those endpoints into a single endpoint.



    We need this application to be highly available, so we want to deploy it to 2 regions (eg West Europe and North Europe).



    As of Nov 2018, the only API Management plan that supports multi-region is the Premium plan that costs 18x the Basic plan. The Premium plan is way out of our budget.



    We had the idea to setup two Basic API Management units, one for each region, having both configurations synchronized, and placing a Traffic Manager in front of both.



    Assuming that we will only use the gateway functionality of API Management (not developer/publisher portal, authentication etc), what will we be missing with our "Poor Man's Multi Region" solution instead of going with the "native" multi-region of the Premium plan?










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      We have an application built of multiple Logic Apps. We will use Azure API Management to consolidate all those endpoints into a single endpoint.



      We need this application to be highly available, so we want to deploy it to 2 regions (eg West Europe and North Europe).



      As of Nov 2018, the only API Management plan that supports multi-region is the Premium plan that costs 18x the Basic plan. The Premium plan is way out of our budget.



      We had the idea to setup two Basic API Management units, one for each region, having both configurations synchronized, and placing a Traffic Manager in front of both.



      Assuming that we will only use the gateway functionality of API Management (not developer/publisher portal, authentication etc), what will we be missing with our "Poor Man's Multi Region" solution instead of going with the "native" multi-region of the Premium plan?










      share|improve this question













      We have an application built of multiple Logic Apps. We will use Azure API Management to consolidate all those endpoints into a single endpoint.



      We need this application to be highly available, so we want to deploy it to 2 regions (eg West Europe and North Europe).



      As of Nov 2018, the only API Management plan that supports multi-region is the Premium plan that costs 18x the Basic plan. The Premium plan is way out of our budget.



      We had the idea to setup two Basic API Management units, one for each region, having both configurations synchronized, and placing a Traffic Manager in front of both.



      Assuming that we will only use the gateway functionality of API Management (not developer/publisher portal, authentication etc), what will we be missing with our "Poor Man's Multi Region" solution instead of going with the "native" multi-region of the Premium plan?







      azure azure-api-management






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 9 at 12:59









      Victor

      7,842186391




      7,842186391
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          Whatever you will have to build will be missing (as you pointed out):




          1. Configuration synchronization - you will have to make sure that configuration is synchronized between multiple services.

          2. Traffic Manager - you will have to have TM or something else on top of services to reroute traffic in case of DR.

          3. Scale and everything else from this list: https://azure.microsoft.com/en-us/pricing/details/api-management/






          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%2f53226170%2fazure-api-management-poor-mans-multi-region-using-basic-standard-plans%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








            up vote
            1
            down vote













            Whatever you will have to build will be missing (as you pointed out):




            1. Configuration synchronization - you will have to make sure that configuration is synchronized between multiple services.

            2. Traffic Manager - you will have to have TM or something else on top of services to reroute traffic in case of DR.

            3. Scale and everything else from this list: https://azure.microsoft.com/en-us/pricing/details/api-management/






            share|improve this answer

























              up vote
              1
              down vote













              Whatever you will have to build will be missing (as you pointed out):




              1. Configuration synchronization - you will have to make sure that configuration is synchronized between multiple services.

              2. Traffic Manager - you will have to have TM or something else on top of services to reroute traffic in case of DR.

              3. Scale and everything else from this list: https://azure.microsoft.com/en-us/pricing/details/api-management/






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                Whatever you will have to build will be missing (as you pointed out):




                1. Configuration synchronization - you will have to make sure that configuration is synchronized between multiple services.

                2. Traffic Manager - you will have to have TM or something else on top of services to reroute traffic in case of DR.

                3. Scale and everything else from this list: https://azure.microsoft.com/en-us/pricing/details/api-management/






                share|improve this answer












                Whatever you will have to build will be missing (as you pointed out):




                1. Configuration synchronization - you will have to make sure that configuration is synchronized between multiple services.

                2. Traffic Manager - you will have to have TM or something else on top of services to reroute traffic in case of DR.

                3. Scale and everything else from this list: https://azure.microsoft.com/en-us/pricing/details/api-management/







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 3 at 18:44









                Vitaliy Kurokhtin

                2,0671107




                2,0671107






























                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f53226170%2fazure-api-management-poor-mans-multi-region-using-basic-standard-plans%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()