In the datacenter, a VLAN can cross physical switches and form a logical L2 domain. Machines, VMs or hosts on this VLAN can communicate with each other irrespective of its physical location with private IP addresses. All is secure.
The question is: Can you stretch this VLAN to AWS or Azure?
Yes, you can.
Aviatrix stretches your VLAN to public cloud
In the diagram at right, an Aviatrix virtual appliance is deployed on VLAN 10.8.0.0/16. This VLAN is divided into sub-segments, for example 10.8.16.0/20, 10.8.32.0/20, 10.8.48.0/20, where each sub-segment is mapped and becomes the CIDR of VPC or VNET or Google Network. From datacenter point of view, this is as if VLAN 10.8.0.0/16 is stretched to a number of public cloud environments. Servers in datacenter can talk to instances in public cloud as if they are on-prem, via private IP addresses.
This looks interesting.
Workload burst to cloud may be the first use case came to your mind. But in reality we have not found anyone actually doing workload burst.
Customers use this architecture to manage their hybrid cloud deployment and scaling, as an alternative approach to the traditional way of connecting an edge router/firewall appliance to public cloud.
What do they love it about? Many things.