Polaris supports cross-region deployment and provides a global registration, configuration, and governance center. It enables the formation of a unified Polaris cluster by networking control nodes across multiple regions within the same large region. For example: within a single Polaris instance, it supports nodes in both Guangzhou and Beijing. With Guangzhou selected as the primary region where Polaris resides, data consistency is guaranteed across multiple regions.
The primary region and secondary regions are identical in terms of client access and usage, both providing service registration and discovery capabilities. Data is ultimately stored in the primary region.
Scenarios
Scenario 1: Cross-Region Service Registration and Discovery
Polaris provides cross-region service registration and discovery, meeting the scenarios of cross-region service invocation for business services. In scenarios such as e-commerce and gaming, businesses typically deploy services across multiple regions to improve system stability and reduce customer access time. However, due to the specificity of certain business scenarios or the complexity of data synchronization, some services cannot be deployed in multiple regions and require cross-region service invocation. For example: in an e-commerce application, a service in the Beijing region accesses a service in the Shanghai region.
Polaris supports intra-city proximity-based routing and inter-city disaster recovery. In cross-region disaster recovery scenarios, a service deploys nodes in two regions. Under normal circumstances, traffic is routed to the nearest region. If a failure occurs in one region, traffic is routed to the other region. For example: when providers in Guangzhou become unavailable, consumers will invoke providers in Shanghai across regions.
Operation Steps
Step 1: Cross-Region Node Networking.
1. Log in to TSF console, then in the left menu bar select Polaris (North Star) and go to the engine instance list page.
2. Click New to create an instance. For details, refer to Engine Management.
Select the deployment architecture cross-city multi-AZ, select the cross-region target region, and configure the number of client access nodes and cluster network information for each regional cluster.
