Help Center/ Multi-Site High Availability Service/ Service Overview/ Edition Differences
Updated on 2025-11-03 GMT+08:00
View PDF
Share

Edition Differences

Function Modules

You can choose the Intra-city multi-active or Remote multi-active module.

Intra-city multi-active provides the following Features:

  • MySQL
  • Oracle
  • PostgreSQL
  • Redis
  • MongoDB
  • Elasticsearch
  • openGauss
  • API

Remote multi-active provides the following Features:

  • MySQL
  • Oracle
  • PostgreSQL
  • Redis
  • MongoDB
  • Elasticsearch
  • openGauss
  • API

Table 1 lists the details.

Table 1 Function modules

Edition

Feature

Intra-city multi-active

Deploy your subsystems in the same region and less than 50 km from each other.

  • Service continuity: real-time traffic balancing and fast failover
  • Horizontal scaling: rapid service development
  • Traffic isolation: flexible traffic scheduling
  • Cost-effectiveness: higher resource utilization with fewer redundancy costs

Remote multi-active

Deploy at least one subsystem in a different region and more than 300 km from any other subsystem.

  • Service continuity: cross-region DR and multi-active with doubled system capacity and improved SLA
  • Unified management: same architecture, operations, and multi-active management for the two DCs
  • Switchable workflows: automatic failover and DR with default/custom workflows
  • Enhanced architecture: zone-based management for smaller fault radius

Multi-Active Instances

You can create Platinum MAS instances. They can be deployed in intra-city multi-active or remote multi-active mode on Huawei Cloud.

Specifications

Table 2 Specifications

Item

Item

Quota

Visible to Tenant

Remarks

MAS (common resources)

Number of namespaces per tenant

≤ 1,000

Yes

A tenant can apply for a maximum of 1,000 namespaces.

Number of data sources per tenant

≤ 200

Yes

Max. 200

Number of data synchronization tasks per tenant

≤ 100

Yes

Max. 100

MAS instances

Number of MAS instances per tenant

≤ 10

Yes

A tenant can create a maximum of 10 MAS instances.

Number of monitors per MAS instance

≤ 100

Yes

Max. 100

Number of applications per MAS instance

≤ 200

Yes

Max. 200

CAST

Number of chaos experiments per project

≤ 10,000

Yes

Max. 10,000

Number of chaos experiment groups per project

≤ 5,000

Yes

Max. 5,000

Number of chaos experiments per group

≤ 100

Yes

Max. 100

Number of chaos experiment executions

N/A

No

N/A

Number of attack objects per hour

N/A

No

N/A

Number of experiments executed per hour

N/A

No

N/A

Octopus

Number of workflows per tenant

≤ 1,000

Yes

A tenant can create a maximum of 1,000 workflows.

Number of tasks per workflow

≤ 200

Yes

A workflow can contain a maximum of 200 tasks.

HAP

Number of risk scenarios per tenant

≤ 100

Yes

Max. 100

Number of emergency plans per tenant

≤ 100

Yes

Max. 100

Number of execution orders running concurrently per tenant

≤ 5

Yes

Max. 5

Number of risk events running concurrently per tenant

≤ 20

Yes

Max. 20

Number of steps per emergency plan

≤ 10

Yes

Max. 10