- Implementing DevOps with Microsoft Azure
- Mitesh Soni
- 345字
- 2021-07-02 23:28:22
Traffic Manager
Microsoft Azure Traffic Manager provides a feature to distribute user traffic to different endpoints. These endpoints can be Azure App Service (Azure Web Apps), cloud services, Azure Virtual Machines, and external endpoints. It is a DNS-based traffic routing. Azure Traffic Manager supports three traffic routing methods to decide how traffic can be routed to different endpoints. In simple terms, it is a way to decide which endpoint should serve the DNS request.
There are two different deployment models in Microsoft Azure—the classic deployment and Resource Manager deployment models. Microsoft Azure Traffic Manager uses different terminology for traffic routing methods (known as the load-balancing method in the classic deployment model):
- Priority method (Failover method): Select the Priority or Failover method for traffic routing when you need resources in a specific region to serve all the traffic and only use other endpoints if the main endpoint is unavailable.

Often this method is cost-optimized and the usage of the application is very well known and specific to a region.
- Weighted method (Round-robin method): Select the Weighted or Round-robin method for traffic routing when you need resources to serve in a different region or across a set of different endpoints.

Let's say we know that our application hosted in Azure Web Apps is going to be equal or in a specific ratio, then the Weighted method can be more appropriate.
- Performance method: Select Performance for the traffic routing method when we want to provide equal performance to the user of the resources hosted in Azure.

So, in simple terms, users will be redirected to the nearest endpoint to serve the response.
Some benefits of Microsoft Azure Traffic Manager are as follows:
- Easy to use and configure
- Easy learning curve
- Configuration is available from Azure Portal as well as Azure PowerShell
- DNS level traffic routing
- Helps in high availability of the business critical application
- Provides automatic failover
- Supports multiple endpoints: Microsoft Azure and external endpoints
- Helps to support the scenario of planned maintenance
- We can combine hybrid applications as it supports multiple endpoints
- 企業(yè)大數(shù)據(jù)系統(tǒng)構(gòu)建實(shí)戰(zhàn):技術(shù)、架構(gòu)、實(shí)施與應(yīng)用
- 大數(shù)據(jù):規(guī)劃、實(shí)施、運(yùn)維
- 數(shù)據(jù)化網(wǎng)站運(yùn)營(yíng)深度剖析
- 數(shù)據(jù)驅(qū)動(dòng)設(shè)計(jì):A/B測(cè)試提升用戶體驗(yàn)
- OracleDBA實(shí)戰(zhàn)攻略:運(yùn)維管理、診斷優(yōu)化、高可用與最佳實(shí)踐
- Oracle PL/SQL實(shí)例精解(原書(shū)第5版)
- SQL應(yīng)用及誤區(qū)分析
- 大數(shù)據(jù)精準(zhǔn)挖掘
- SQL Server 2012數(shù)據(jù)庫(kù)管理教程
- Oracle RAC日記
- Python數(shù)據(jù)分析與數(shù)據(jù)化運(yùn)營(yíng)
- MySQL數(shù)據(jù)庫(kù)技術(shù)與應(yīng)用
- Oracle高性能SQL引擎剖析:SQL優(yōu)化與調(diào)優(yōu)機(jī)制詳解
- 離線和實(shí)時(shí)大數(shù)據(jù)開(kāi)發(fā)實(shí)戰(zhàn)
- Oracle 11g數(shù)據(jù)庫(kù)管理與開(kāi)發(fā)基礎(chǔ)教程