官术网_书友最值得收藏!

High Availability across Azure regions

The architecture shown next, shows similar deployments on two different Azure regions. Both the regions have the same resources deployed. High Availability is designed at individual resource level within these regions. There are multiple virtual machines at each tier connected through the load balancer and they are part of the availability set. These virtual machines are placed on separate fault and update domains. While the web servers are connected to external load balancers, the rest of the tiers such as application and database tiers have internal load balancers. It is to be noted that application load balancers could have been used for web servers and application tiers instead of Azure load balancer if there is a need for advanced services such as session affinity, SSL termination, advance security using WAF, and path-based routing. Databases in both the regions are connected to each other using VNET peering and gateways. This is helpful in configuring log shipping, SQL Server AlwaysOn, and other data synchronization techniques.

Endpoints of load balancers from both the regions are used to configure Traffic Manager endpoints and traffic is routed based on priority load balancing method. Traffic Manager helps in routing all requests to the East US region and failover to West Europe in case of non-availability of the first region.

主站蜘蛛池模板: 祁连县| 青铜峡市| 融水| 荣昌县| 公安县| 惠东县| 吉隆县| 锡林郭勒盟| 黄陵县| 赞皇县| 萍乡市| 琼海市| 古交市| 惠安县| 额济纳旗| 万年县| 重庆市| 江华| 吉林省| 巴南区| 缙云县| 嘉荫县| 南澳县| 饶河县| 玉环县| 榆中县| 临沭县| 清徐县| 中牟县| 佳木斯市| 西林县| 郑州市| 青川县| 万荣县| 鹤岗市| 武城县| 桃园市| 吉隆县| 白沙| 鹿泉市| 涿州市|