Hub and spoke networking describes a scalable, flexible network topology which fits many cloud environments. It comprises a single Hub network which controls connectivity to on-premises networks and the Internet, alongside a series of Spoke networks which house specific workloads.
The role of the Hub and spoke networking component is to deliver:
- Separation of concerns via network isolation of workloads, which in turn enables:
- Stable change management (changes can happen in spokes without affecting other services)
- Independent specialist teams to manage workloads within a specific spoke
- Centralised provision of management services, forming:
- A consistent control plane for system connectivity and management
- Cost-effective deployment and management of infrastructure-oriented appliances and tools
Note that networking can be used to provide connectivity to PaaS services, as well as IaaS based services such as Virtual Machines.
Additional shared services can be deployed into the Hub network, including:
- Virtual Appliances for security operations, for example Network Taps, Intrusion Detection Systems, and standalone SIEM tools.
- Load-balanced identity services. For exampl, ADFS may be deployed for improved SSO user experiences (recommended only where direct integration to Azure AD is unavailable)
- Domain Services, and solutions to manage resources in spokes (licensing optimisation platforms, security suites)
Cloudmarque workload components use a service locator pattern to identify the services they provide and specify dependencies. This component provides and relies on the following services:
- Networks - Provides a series of subnets which can be used by other cloud resources such as Virtual Machines, Containers, and PaaS resources (storage, web apps, etc).
- Logging - A logging service is required as a target for network alerts.
Edit this page on GitHub
The content on this page is published under Open Source licenses via GitHub. To submit issues or provide feedback please visit the repository.Visit