Future Networks, Services and Management by Unknown

Author:Unknown
Language: eng
Format: epub
ISBN: 9783030819613
Publisher: Springer International Publishing

Where peering becomes too complex to manage is where users deploy ten or more VPCs that require interconnectivity. While a user might start out with only one or two VPCs that require connectivity, this often snowballs into most if not all VPCs needing connectivity. The architecture that results from all VPCs needing connectivity is the full mesh architecture, and in this case, the number of peering connections is equal to n being the number of VPCs, and number of peering connections = n(n − 1)/2. This means that 10 VPCs peered together in a full mesh will equal 45 peering connections, and each route table for each VPC will need a route to each VPC, meaning 45 manually created routes need to be deployed in each VPCs route table. Due to the complexity of the full mesh deployment, users of the cloud will sometimes default to a hub and spoke peering architecture, with centrally hosted shared services in a central VPC, and peering connection to each application that resides in a spoke. Figure 7.11 shows both the full-mesh and hub-and-spoke peering architectures commonly used.

Fig. 7.11Full-mesh and hub-and-spoke peering topologies

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.