none
Highly available backend using Azure API App Services. RRS feed

  • Question

  • What is the preferred way to connect Azure API App Services hosted in different regions for high availability with API Management? We deploy multiple web/api app services in different regions to protect against Azure maintenance windows. Currently these are fronted by Azure Traffic Manager. Going forward with API Management would the best practice just to point the backend URL to the Traffic Manager or is there some other configuration that makes more sense?
    Thursday, September 1, 2016 4:44 PM

Answers

  • Hi William

    The recommendation is as you say above (even better if you can deploy an APIM endpoint in the same region as the API backend) - point APIM to the Traffic Manager endpoint - while this adds a small latency the first time it is called, once the value is cached, it should make no difference. This makes setup and maintenance very simple.

    Matt

    • Proposed as answer by Swikruti Bose Monday, September 5, 2016 4:53 PM
    • Marked as answer by William W Murphy Wednesday, September 7, 2016 2:00 PM
    Thursday, September 1, 2016 5:20 PM

All replies

  • Hi William

    The recommendation is as you say above (even better if you can deploy an APIM endpoint in the same region as the API backend) - point APIM to the Traffic Manager endpoint - while this adds a small latency the first time it is called, once the value is cached, it should make no difference. This makes setup and maintenance very simple.

    Matt

    • Proposed as answer by Swikruti Bose Monday, September 5, 2016 4:53 PM
    • Marked as answer by William W Murphy Wednesday, September 7, 2016 2:00 PM
    Thursday, September 1, 2016 5:20 PM
  • In a multi region API Management scenario, would you use a Geo-IP Traffic manager or pairs of counter configured Fail-Over Traffic Managers. We're not there yet but we do have a usage point that Multi-Region Premium API Management is where we're going to be.
    Wednesday, September 7, 2016 2:04 PM