Multi-Cloud Networks
Enterprises that require multi-cloud networking typically deploy Layer 2 or Layer 3
switches on cloud exchanges in colocation facilities close to cloud regions. They route
the traffic through direct cloud connectivity services, such as AWS Direct Connect or
Azure ExpressRoute.
But with the rise of transit gateways, you can simplify the connectivity between cloud
providers. For example, the Aviatrix gateway enables softwareË—defined, encrypted
IPSec tunnel connections directly between different cloud provider networks without
going through cloud exchanges or Multiprotocol Label Switching (MPLS) circuits.
Connecting two cloud environments helps organizations create application portability.
For instance, if you are building a point of sale application that cannot allow any down-
time, you can port all of your workloads over to Azure if AWS goes down, or vice versa.
If you are building an application that requires network connectivity across multiple
cloud providers, you can do that, or you can pick and choose which service you want,
rather than get locked into one cloud provider.
Value in Staying Old-School
Is there still some value in managing MVC connections using the old configuration
model? Sometimes there is.
You have to look at it on a case-by-case basis. If you already have an established VNet
peering setup across networks, or if you have already implemented a transit VPC using
Cisco CSR, etc., it might require significant effort and downtime to switch over to transit
gateway solutions.
22 | THE DOPPLER |
SUMMER 2019