Considerations | Select plan |
Geographic location | To reduce latency and improve access speed, we recommend that you purchase Kafka instance that is closest to your region. |
Private network connectivity | If your service requires private network isolation, deploy across different regions. If your service requires private network communication, deploy within the same region. |
Resource price | Resource prices may vary across regions. Choose based on your budget on the purchase page. |
Considerations | Select plan |
Disaster recovery capability | If you need higher disaster recovery capability, deploy your business in different availability zones to ensure fault isolation and achieve cross-availability zone disaster recovery. |
Network latency | If you need lower latency, we recommend that you purchase Kafka instances within the same availability zone. |
Region | RegionID | Availability zone | ZoneID | Status |
North China 2 (Beijing) | cn-beijing | Availability zone A | cn-beijing-a | Official sale |
| | Availability zone B | cn-beijing-b | |
| | Availability zone C | cn-beijing-c | |
| | Availability zone D | cn-beijing-d | |
East China 2 (Shanghai) | cn-shanghai | Availability zone A | cn-shanghai-a | Official sale |
| | Availability zone B | cn-shanghai-b | |
| | Availability zone C | cn-shanghai-c | |
South China 1 (Guangzhou) | cn-guangzhou | Availability zone A | cn-guangzhou-a | Official sale |
| | Availability zone B | cn-guangzhou-b | |
| | Availability zone C | cn-guangzhou-c | |
Hong Kong, China | cn-hongkong | Availability zone A | cn-hongkong-a | Official sale |
| | Availability zone B | cn-hongkong-b | |
Asia Pacific Southeast (Johor) | ap-southeast-1 | Availability zone A | ap-southeast-1a | Official sale |
| | Availability zone B | ap-southeast-1b | |