Operating in multiple geographic locations places workloads closer to end users.
You use ROBO sites to support manufacturing, Point of Sale (POS), medical facilities such as hospitals and clinics, or in other scenarios. You manage these locations by using a hub-spoke method where you usually define regions by geographic location.
Hubs act as a central point of management for all connected ROBO sites.
You can scale ROBO sites according to changes in business needs, such as mergers and acquisitions.
Disaster recovery is possible in a hub between regions. Data collection from and provisioning to the ROBO site is uninterrupted.
You can create and monitor regional SLA dashboards in a hub to identify investment opportunities in a ROBO site.
This design uses a hub that can fail over between San Francisco (SFO) and Los Angeles (LAX).
Hub represents the centralized provisioning and monitoring components of the Standard SDDC. The hub can be dedicated to ROBO sites according to the number of ROBO connections required, or be part of a larger SDDC platform. In either case, it can fail over between regions if a disaster occurs or for disaster avoidance. See Deployment Models of Remote Office and Branch Office.
Remote and Branch Offices
A remote or branch office is defined as a small location with limited data center capabilities providing specific services to the site. It usually supports up to 100 virtual workloads in the SDDC. ROBO sites have lower SLA and connectivity requirements. If a connectivity failure occurs, they operate independently from the hub .
This design uses a single ROBO site that is located in New York City (NYC).