Glossary
This topic lists the key terms for Application High Availability Service (AHAS).
Terms related to active-active and disaster recovery
Intra-city active-active
An architecture where two data centers are deployed in the same city to provide services in parallel.
Active geo-redundancy
An architecture where multiple data centers are deployed in different cities. All data centers are active and serve traffic in parallel. This model fully utilizes resources and prevents backup centers from being idle. If a data center fails, the other data centers take over its services to ensure business continuity without disrupting users.
Three data centers across two regions
An architecture that includes three interconnected data centers: a production data center, an intra-city disaster recovery center, and a remote disaster recovery center. If one data center fails, the others take over its services.
Namespace
An MSHA Namespace is a logical tenant used for tenant-level management, configuration, and resource isolation. Examples include a staging environment for transaction units, a production environment for transaction units, and a staging environment for shopping guide units.
MSFE
MSFE (MSHA-FRONT-END) is the access layer that distributes and modifies incoming traffic.
routeId
A routing flag that can be static or dynamic. A static routing flag uses static properties, such as account IDs or locations, as input for route computing. A dynamic routing flag is defined by the business system.
RPO
RPO (recovery point objective) is the maximum amount of data loss that a system can tolerate, measured in time. This objective specifies the point in time to which system data must be recovered after a disaster. A lower RPO value means that less data loss is tolerable.
RTO
RTO (recovery time objective) is the maximum amount of time that a service can be unavailable after a disaster. A lower RTO value means the service is more critical and must be restored more quickly.