Skip to content

Commit ebdd2d9

Browse files
authored
Remove comparison table for network connectivity options
Removed the comparison table for network connectivity options, including benefits and challenges.
1 parent 9500099 commit ebdd2d9

1 file changed

Lines changed: 0 additions & 9 deletions

File tree

learn-pr/wwl-azure/design-network-solutions/includes/5-design-for-premises-connectivity-to-azure-virtual-networks.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -38,12 +38,3 @@ The Azure Virtual WAN architecture includes the benefits of standard hub-spoke n
3838
- Mixed use of user VPN to the site
3939
- Virtual network-to-network connectivity
4040

41-
## Compare services
42-
43-
The following table compares the benefits and challenges of the network connectivity options. Review the scenarios, and think about which services can enhance the network solution for Tailwind Traders.
44-
45-
| Compare | Azure VPN Gateway | Azure ExpressRoute | ExpressRoute + VPN failover | Azure Virtual WAN + hub-spoke |
46-
| --- | --- | --- | --- | ---
47-
| **Benefits** | - Simple to configure <br> - High bandwidth available (up to 10 Gbps depending on VPN Gateway SKU) | - High bandwidth available (up to 10 Gbps depending on connectivity provider) <br> - Supports dynamic scaling of bandwidth to help reduce costs during periods of lower demand (not supported by all connectivity providers) <br> - Enables direct organizational access to national clouds (depends on connectivity provider) | - High availability if ExpressRoute circuit fails (fallback connection on lower bandwidth network | - Reduced operational overhead by replacing existing hubs with fully managed service <br> - Cost savings by using managed service, which removes need for NVA <br> - Improved security via centrally managed secured hubs with Azure Firewall and Virtual WAN <br> - Separates concerns between central IT (SecOps, InfraOps) and workloads (DevOps) |
48-
| **Challenges** | - Requires on-premises VPN device | - Can be complex to set up <br> - Requires working with non-Microsoft connectivity provider <br> - Provider responsible for provisioning network connection <br> - Requires high-bandwidth routers on-premises | - Complex to configure <br> - Must set up both VPN connection and ExpressRoute circuit <br> - Requires redundant hardware (VPN appliances) <br> - Requires redundant Azure VPN Gateway connection for which you pay charges | **Note**: Azure Virtual WAN is designed to reduce previously listed connectivity challenges. |
49-
| **Scenarios** | - Hybrid apps with light traffic between on-premises hardware and the cloud <br><br> - Able to trade slightly extended latency for flexibility and processing power of the cloud | - Hybrid apps running large-scale, mission-critical workloads that require high degree of scalability | - Hybrid apps that require higher bandwidth of ExpressRoute and highly available network connectivity | - Connectivity among workloads requires central control and access to shared services <br><br> - Enterprise requires central control over security aspects like a firewall and segregated management for workloads in each spoke |

0 commit comments

Comments
 (0)