Cross Cloud Networking
One crucial component of cloud architecture is the integration of hybrid environments with the cloud. There are multicloud environments that require communication in addition to on-premises environments. Google cloud examine a few Cross Cloud Networking hub-and-spoke communication reference architectures in this blog.
The power of Cross-Cloud Network
It is necessary to have inter-network connectivity as your cloud projects expand and you add more networks. In order to connect your dispersed apps, Cross-Cloud Network offers a suite of features and designs for any-to-any communication that make use of Google’s software-defined global scaled backbone.
Let’s examine two architectural patterns: Network Connectivity Center-based and VPC Network Peering-based.
Inter-VPC communication with VPC Network Peering example pattern
Google cloud examine the passage of a packet from an external network to an application situated in workload VPC network 1 in Google Cloud to gain an understanding of how to approach network design. The utilization of VPC Network Peering is the main focus of this architecture. The Google Cloud network (transit VPC, services access VPC, managed services VPC, workloads VPC) and an external network (on-premises and other clouds) make up the network.
The end-to-end solution of this design makes use of the following services:
- Cloud Interconnect (Direct, Partner, Cross-Cloud): This allows you to connect to the transit VPC from your on-premises or other clouds.
- Cloud VPN: To export custom routes from the private services access network and connect from the service-access VPC to the transit VPC
- To connect from workload, use VPC Network Peering. VPC to transit VPC
- Access to private services: To establish a private connection to managed services, use the services access VPC
- To expose services in the managed services VPC network for consumption in the services access VPC, use Private Service Connect.
- VPC spokes in the Network Connectivity Center: To enable connectivity between workload VPCs when required
Please study the complete architectural document reference guide: Cross-Cloud Network inter-VPC connectivity utilizing VPC Network Peering to comprehend more precise information like route exchange and packet flow.
Inter-VPC communication with Network Connectivity Center
Let’s employ a Network Connectivity Center with interconnect spokes and a star layout in this more contemporary design. Let’s examine the flow of a packet from an external network to an application situated in the workload VPC in order to gain an understanding of how to construct your network in this arrangement.
The Google Cloud network (transit VPC, service access Virtual Private Cloud(VPC), managed services VPC, Private Service Connect consumer VPC, and workload VPC) and an external network (on-premises and other clouds) make up the network.
The end-to-end solution offered by this design makes use of the following services.
- Cloud Interconnect (Direct, Partner, Cross-Cloud): This allows you to connect to the transit VPC from your on-premises or other clouds. In this instance, several external places in various regions are joining.
- Cloud VPN: To export custom routes from the private services access network and connect from the service access VPC to the transit VPC
- To connect from workload, use Virtual Private Cloud(VPC) Network Peering. VPC to transit VPC
- Access to private services: To establish a private connection to managed services, use the services access VPC
- Private Service Connect: Private Service Connect consumer VPC with endpoints to service made available to connected peers; exposes services in the managed services VPC network to be consumed in the services access VPC.
- VPC spokes in the Network Connectivity Center: To enable connectivity between workload VPCs when required
- Network Connectivity Center topology: Uses pre-configured topologies (you can select mesh or star based on your needs).
Please study the complete architecture document reference guide: Cross-Cloud Network inter-VPC connectivity utilizing Network Connectivity Center to comprehend the specifics, including the Network Connectivity Center star topology, route exchange, and packet flow.
