This topic describes the concepts of Alibaba Cloud regions and zones. This topic also describes how to select regions and zones and provides a list of regions and zones that are supported by Alibaba Cloud Realtime Compute for Apache Flink.
Background information
Regions are geographical locations where Alibaba Cloud data centers are deployed. Regions are divided based on cities where data centers reside. For example, the China (Beijing) region indicates that the data center is located in Beijing, China.
Zones in a region are physical areas that have independent power supplies and network facilities. Fault isolation is applied among zones to prevent the spread of faults and ensure service continuity.
NoteFault isolation is not suitable for major disasters or major power failures.
Precautions
The region and zone that you select when you create a Realtime Compute for Apache Flink workspace cannot be changed after the workspace is created.
You can adjust the availability of resources in different regions based on the resources that are consumed by your business. You may not be able to purchase resources because they are sold out. For more information, see the resources available on the buy page of Realtime Compute for Apache Flink.
Region and zone selection
Item | Description |
Network communication between services | We recommend that you deploy Realtime Compute for Apache Flink in the same zone and region as its upstream and downstream storage services. This way, these cloud services can communicate with each other over the internal network. This reduces access latency and accelerates service access. Note A region consists of multiple zones. Zones in the same region are interconnected over a low-latency internal network. Zones in each region are completely isolated from zones in other regions. |
Resource price | The resource price may vary based on the region. Check the price details on the buy page of Realtime Compute for Apache Flink. We recommend that you select a region based on your budget. |
Network latency | Zones in the same region are interconnected over a low-latency internal network. Zones in each region are completely isolated from zones in other regions. If your region is close to the region in which resources are deployed, the network latency is low and the access speed is fast. We recommend that you evaluate your business requirements to find the balance between high availability and low latency. |
High availability and disaster recovery |
|
Regions and zones
Specific zones in specific regions may be unavailable for purchase and can only be scaled out. The available regions and zones are displayed on the buy page.
Region | Zone |
Singapore | C |
China (Hong Kong) | B and C |
Japan (Tokyo) | B |
Germany (Frankfurt) | B |
Indonesia (Jakarta) | A |
US (Silicon Valley) | B |
US (Virginia) | B |
Malaysia (Kuala Lumpur) | B |
UK (London) | A |
China (Beijing) | F, G, H, and K |
China (Shanghai) | B, F, and G |
China (Shenzhen) | E and F |
China (Hangzhou) | H, I and J |
China (Zhangjiakou) | B |
FAQ
Q: What do I do if a message indicating that resources are sold out appears?
A: Alibaba Cloud Realtime Compute for Apache Flink provides services in multiple regions across the globe. Each region has one or more zones. If resources in the zone that you selected are sold out, use one of the following methods to purchase resources:
Select another region.
Select another zone.
If no resources are available after you change the region or zone, we recommend that you wait for a specific period of time before you purchase resources. Resources are dynamically changed. If resources are insufficient, Alibaba Cloud replenishes resources at the earliest opportunity.