Information on multi-cloud networking, cloud network platform, cloud networking, cloud network security, cloud network operations
Issue link: https://aviatrix.com/resources/i/1321468
2 WHITE PAPER WHITE PAPER Case Study A simple multi-national data network, not uncommon for global enterprises. In this case, two data centers, one in Europe and the other in North America, connected over an MPLS network with several branch offices and partner sites connected to the same network ("initial state"). As an example, when enterprises move applications to cloud, traffic patterns change from branches to on-prem data centers to going directly to the cloud. Additionally, from an architectural perspective most enterprises strive to avoid "tromboning" traffic out of the cloud back to the data center for inspection by moving the DMZ into the cloud. The following architectural scenarios are just examples and are often deploy new approach while maintaining current architecture in parallel. Architectural Scenario A You are tasked with adding 20 new branches and partner sites to your global network (the starting point is the "initial state"). Alternative Architectural Approach • Instead of onboarding the new branches and partner sites to the existing MPLS network, you create a cloud backbone • New branches and partner sites are connected to the cloud backbone using IPSec, entering the cloud backbone at the cloud provider's point-of-presence (POP), closest to the physical location of the branch or partner as possible • Your data centers are connected to the cloud network using private circuit options (e.g. AWS Direct Connect, Azure Express Route, Google Interconnect), to provide high quality connectivity between the new locations and your data centers. • The result: Cost saving and higher quality of the network service Architectural Scenario B Your objective is to eliminate MPLS network costs (starting point is the "initial state", or a next step after scenario A). Alternative Architectural Approach • Retire the MPLS network and associated support contracts for the MPLS Customer Premises Equipment (CPE) • Leverage one or more Cloud providers (AWS, Azure, OCI, GCP) to deliver global transit network connectivity • Connect your data centers to the global transit network using private circuit options (e.g. AWS Direct Connect, Azure Express Route, Google Interconnect) – select the cloud provider with the best presence in your region. • Connect branches and partner sites to global transit network using IPSec, entering the cloud at the cloud provider's point-of-presence (POP), closest to the physical location of the branch or partner as possible • You are now leveraging the multi-cloud network backbone for the entire network • The Result: Cost saving and higher quality of the network service