Mục Lục

Networking on Azure and AWS

Article
11/15/2022
4 minutes to read

Elastic Load Balancing, Azure Load Balancer, and Azure Application Gateway

The Azure equivalent of the Elastic Load Balancing services are:

Load Balancer: Provides the same network layer 4 capabilities as the AWS Network Load Balancer and Classic Load Balancer, allowing you to distribute traffic for multiple VMs at the network level. It also provides a failover capability.
Application Gateway: Offers application-level rule-based routing comparable to the AWS Application Load Balancer.

Route 53, Azure DNS, and Azure Traffic Manager

In AWS, Route 53 provides both DNS name management and DNS-level traffic routing and failover services. In Azure this is handled through two services:

Azure DNS provides domain and DNS management.
Traffic Manager provides DNS level traffic routing, load balancing, and failover capabilities.

Direct connect and Azure ExpressRoute

Azure provides similar site-to-site dedicated connections through its
ExpressRoute service. ExpressRoute allows you to connect your local network directly to Azure resources using a dedicated private network connection. Azure also offers more conventional site-to-site VPN connections at a lower cost.

Route tables

AWS provides route tables that contain routes to direct traffic, from a subnet/gateway subnet to the destination. In Azure, this feature is called user-defined routes.

With user-defined routes, you can create custom or user-defined (static) routes in Azure, to override Azure’s default system routes, or to add more routes to a subnet’s route table.

Private Link

Similar to AWS PrivateLink, Azure Private Link provides private connectivity from a virtual network to an Azure platform as a service (PaaS) solution, a customer-owned service, or a Microsoft partner service.

VPC Peering, Azure VNet Peering

In AWS, a VPC peering connection is a networking connection between two VPCs, which enables you to route traffic between them using private IPv4 addresses or IPv6 addresses.

Azure virtual network (VNet) peering enables you to seamlessly connect two or more Virtual Networks in Azure. The virtual networks appear as one for connectivity purposes. The traffic between virtual machines in peered virtual networks uses the Microsoft backbone infrastructure. Like traffic between virtual machines in the same network, traffic is routed through Microsoft’s private network only.

Content delivery networks – CloudFront and Azure Front Door

In AWS, CloudFront provides CDN services, to globally deliver data, videos, applications, and APIs. This is similar to Azure Front Door.

Azure Front Door is a modern cloud content delivery network (CDN) service that delivers high performance, scalability, and secure user experiences for your content and applications. For a full list of Azure Front Door product offerings, see Overview of Azure Front Door tiers.

Network service comparison

Networking architectures

Deploy highly available NVAs
- 12/08/2018
- 7 min read
Learn how to deploy network virtual appliances for high availability in Azure. This article includes example architectures for ingress, egress, and both.
Hub-spoke network topology in Azure
- 9/30/2020
- 7 min read
Learn how to implement a hub-spoke topology in Azure, where the hub is a virtual network and the spokes are virtual networks that peer with the hub.
Implement a secure hybrid network
- 1/07/2020
- 9 min read
See a secure hybrid network that extends an on-premises network to Azure with a perimeter network between the on-premises network and an Azure virtual network.