You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/3-design-implement-azure-load-balancer-using-azure-portal.yml
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/4-exercise-create-configure-azure-load-balancer.yml
- content: "What are two benefits of Traffic Manager?"
21
+
- content: "The Azure Traffic Manager operates at which OSI model layer?"
20
22
choices:
21
-
- content: "Distribution of traffic and continuous monitoring of endpoint health."
22
-
isCorrect: true
23
-
explanation: "Correct. Distribution of traffic according to one of several traffic-routing methods and continuous monitoring of endpoint health and automatic failover when endpoints fail."
24
-
- content: "Resolution of DNS queries and reduced need for DNS servers."
23
+
- content: "Layer 3"
25
24
isCorrect: false
26
-
explanation: "Incorrect. Traffic Manager uses DNS to direct clients to specific service endpoints based on the rules of the traffic-routing method."
27
-
- content: "Supports one traffic-routing method and integrates with DNS."
25
+
explanation: "Incorrect. Traffic Manager works at the application level, Layer 7 ."
26
+
- content: "Layer 4"
28
27
isCorrect: false
29
-
explanation: "Incorrect. Azure Traffic Manager supports six traffic-routing methods. The traffic-routing method determines which endpoint is returned in the DNS response."
30
-
- content: "Which traffic-routing method should be use when end users need to use the \"closest\" endpoint for the lowest network latency?"
28
+
explanation: "Incorrect. Traffic Manager works at the application level, Layer-7."
29
+
- content: "Layer 7"
30
+
isCorrect: true
31
+
explanation: "Correct. Traffic Manager works at the application level, Layer-7."
32
+
- content: "Which traffic-routing method provides the lowest network latency by selecting the users closest location?"
31
33
choices:
32
34
- content: "Performance"
33
35
isCorrect: true
34
-
explanation: "Correct. Use for endpoints in different geographic locations, and you want end users to use the \"closest\" endpoint for the lowest network latency."
36
+
explanation: "Correct. Performance routing uses the closest endpoint for the lowest network latency."
35
37
- content: "Geographic"
36
38
isCorrect: false
37
-
explanation: "Incorrect. Select this routing method to direct users to specific endpoints (Azure, External, or Nested) based on where their DNS queries originate from geographically."
39
+
explanation: "Incorrect. Geographic routing directs users to specific endpoints based on where the query originated."
38
40
- content: "Priority"
39
41
isCorrect: false
40
-
explanation: "Incorrect. Select this routing method for one primary service endpoint for all traffic. You can provide multiple backup endpoints in case the primary or one of the backup endpoints is unavailable."
42
+
explanation: "Incorrect. Priority routing directs all traffic to one primary service endpoint."
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/6-exercise-create-traffic-manager-profile-using-azure-portal.yml
The term load balancing refers to the even distribution of workloads (that is, incoming network traffic), across a group of backend computing resources or servers. Load balancing aims to optimize resource use, maximize throughput, minimize response time, and avoid overloading any single resource. It can also improve availability by sharing a workload across redundant computing resources.
1
+
The term load balancing refers to the even distribution of incoming network workloads to a group of backend computing resources or servers. Load balancing aims to optimize resource use, maximize throughput, minimize response time, and avoid overloading any single resource. Load balancing can also improve availability by sharing a workload across redundant computing resources.
2
2
3
3
## Load Balancing options for Azure
4
4
5
5
Azure provides various load balancing services that you can use to distribute your workloads across multiple computing resources, but the following are the main services:
6
6
7
-
-**Azure Load Balancer** - High-performance, ultra-low-latency Layer 4 load-balancing service (inbound and outbound) for all UDP and TCP protocols. The load balancer can handle millions of requests per second ensuring your solution is highly available. Azure Load Balancer is zone-redundant, ensuring high availability across Availability Zones.
8
-
-**Traffic Manager** - DNS-based traffic load balancer that enables you to distribute traffic optimally to services across global Azure regions, while providing high availability and responsiveness. Because Traffic Manager is a DNS-based load-balancing service, it load-balances only at the domain level. For that reason, it can't fail over as quickly as Front Door, because of common challenges around DNS caching and systems not honoring DNS time-to-live values (TTLs).
9
-
-**Azure Application Gateway** - Provides application delivery controller (ADC) as a service, offering various Layer 7 load-balancing capabilities. Use it to optimize web farm productivity by offloading CPU-intensive SSL termination to the gateway.
10
-
-**Azure Front Door** - Application delivery network that provides global load balancing and site acceleration service for web applications. It offers Layer 7 capabilities for your application like SSL offload, path-based routing, fast failover, caching, etc. to improve performance and high-availability of your applications.
7
+
-**Azure Load Balancer**. High-performance, ultra-low-latency Layer 4 load-balancing service (inbound and outbound) for all UDP and TCP protocols. The load balancer can handle millions of requests per second ensuring your solution is highly available. Azure Load Balancer is zone-redundant, ensuring high availability across availability zones.
8
+
-**Traffic Manager**. DNS-based traffic load balancer that enables you to distribute traffic optimally to services across global Azure regions, while providing high availability and responsiveness. Because Traffic Manager is a DNS-based load-balancing service, it load-balances only at the domain level. For that reason, it can't fail over as quickly as Front Door.
9
+
-**Azure Application Gateway**. Provides application delivery controller (ADC) as a service, offering various Layer 7 load-balancing capabilities. Use it to optimize web farm productivity by offloading CPU-intensive SSL termination to the gateway.
10
+
-**Azure Front Door**. Application delivery network that provides global load balancing and site acceleration service for web applications. It offers Layer 7 capabilities for your application. Front Door includes SSL offload, path-based routing, fast failover, and caching.
11
11
12
12
## Categorizing load balancing services
13
13
14
14
Load balancing services can be categorized in two ways: global versus regional, and HTTP(S) versus non-HTTP(S).
15
15
16
16
### Global versus regional
17
17
18
-
**Global** load-balancing services distribute traffic across regional backends, clouds, or hybrid on-premises services. These services route end-user traffic to the closest available backend. They also react to changes in service reliability or performance, in order to maximize availability and performance. You can think of them as systems that load balance between application stamps, endpoints, or scale-units hosted across different regions/geographies.
18
+
**Global** load-balancing services distribute traffic across regional backends, clouds, or hybrid on-premises services. These services route end-user traffic to the closest available backend. They also react to changes in service reliability or performance. You can think of them as systems that load balance between application stamps, endpoints, or scale-units hosted across different regions/geographies.
19
19
20
20
In contrast, **Regional** load-balancing services distribute traffic within virtual networks across virtual machines (VMs) or zonal and zone-redundant service endpoints within a region. You can think of them as systems that load balance between VMs, containers, or clusters within a region in a virtual network.
21
21
@@ -25,52 +25,47 @@ In contrast, **Regional** load-balancing services distribute traffic within virt
25
25
26
26
In contrast, **non-HTTP(S)** load-balancing services can handle non-HTTP(S) traffic and are recommended for nonweb workloads.
27
27
28
+
> [!IMPORTANT]
29
+
> In this module, we're focusing on the non-HTTP(S) solutions.
30
+
28
31
This table summarizes these categorizations for each Azure load balancing service.
29
32
30
33
| Service | Global/regional | Recommended traffic |
| Azure Load Balancer | Regional or Global | non-HTTP(S) |
38
+
| Azure Load Balancer | Regional | non-HTTP(S) |
39
+
36
40
37
41
38
42
## Choosing a load balancing option for Azure
39
43
40
-
Here are the key factors to choosing a load balancing option.
44
+
Here are the key factors to decide on a load balancing option.
41
45
42
46
-**Type of traffic** - is it for a web application? Is it a public-facing or private application?
43
47
-**Scope** - do you need to load balance virtual machines and containers within a virtual network, or load balance across regions, or both?
44
48
-**Availability** - what is the Service Level Agreement (SLA) for the service?
45
49
-**Cost** - In addition to the cost of the actual service itself, consider the operational cost to manage and maintain a solution built on that service. See [Load balancing pricing](https://azure.microsoft.com/pricing/details/load-balancer/).
46
50
-**Features and limitations** - what features and benefits does each service provide, and what are its limitations? See [Load balancer limits](/azure/azure-resource-manager/management/azure-subscription-service-limits).
47
51
48
-
This flowchart helps you select the most appropriate load-balancing solution for your application.
52
+
This [flowchart](/azure/architecture/guide/technology-choices/load-balancing-overview#decision-tree-for-load-balancing-in-azure) helps you select the most appropriate load-balancing solution for your application.
49
53
50
54
:::image type="content" source="../media/load-balancing-decision-tree-3f132096.png" alt-text="flow chart to help select a load-balancing solution for your application.":::
51
55
56
+
> [!TIP]
57
+
> You should use this flowchart and the suggested recommendation only as a starting point. A completed solution can incorporate two or more load-balancing solutions.
52
58
53
-
**As every application has its own unique requirements, you should only use this flowchart and the suggested recommendation as a starting point.**
59
+
## How to select a non-HTTP(S) load balancing solution (video)
54
60
55
-
**If your application consists of multiple workloads, evaluate each workload separately. A complete solution may incorporate two or more load-balancing solutions.**
61
+
This video reviews how to select a loadbalancing solution.
56
62
57
-
## Selecting a load balancing solution by using the Azure portal
- Answer the Yes or No questions on this page to get a recommended solution. The final recommended solution may be a combination of multiple load balancing services.
You can use the **Azure Load Balancing** page in the Azure portal to help guide you to a load-balancing solution. Search for and select **Load balancing - help me choose**. The wizard provides an interactive way to select a load balancing solution.
73
69
74
-
- Optionally, you can also click the **Service comparison** or **Tutorial** tabs for more information and training on the different load balancing services.
75
-
76
-
Now let's look at each of the main Azure load balancing services in more detail.
0 commit comments