All Products
Search
Document Center

Scenarios

Last Updated: Sep 14, 2018

GTM can be used in the following scenarios:

Scenario 1: IP disaster recovery using a primary-standby architecture

In the simplest case, one application service has two IP addresses: A and B. Normally, users access IP address A. When IP address A becomes unavailable, users are expected to access IP address B.

When GTM is enabled, you need to create two address pools A and B, add the IP addresses A and B to these address pools respectively, and configure health check settings. In the access policy, set the default address pool to address pool A and set the failover address pool to address pool B. This enables IP disaster recovery using a primary-standby architecture for the application service.

Scenario 2: Multiple active IP addresses of an application service

In the simplest case, one application service has three IP addresses A, B, and C that are available to users simultaneously. When the three IP addresses are valid, the DNS resolves the service domain to these three IP addresses simultaneously. When one of the three IP addresses becomes unavailable, this invalid IP address is deleted from the DNS list and not returned to users. When this IP address becomes valid, it is added to the DNS list again.

When GTM is enabled, you need to add the IP addresses A, B, and C to an address pool and configure health check to enable multiple active IP addresses for an application service.

Scenario 3: Load balancing for high-concurrency applications

During major online promotion campaigns such as the Single’s day shopping spree, enterprises need to scale up their services temporarily to handle user requests that can be several times larger in volume. Generally, enterprises purchase multiple SLB instances in the same region and use different IP addresses to balance the traffic.

When GTM is enabled, you can add a maximum of 20 IP addresses for each service to perform load balancing. Besides, you can set weights for IP addresses based on their service capability to enable differentiated services.

Scenario 4: Quick access in different regions

When your service scales up, you will need to provide service nationwide or globally. The network conditions in different regions vary and the network access can be restricted by distance and other factors. Therefore, enterprises create service endpoints in the core zones of large regions. Users in different regions can then access the endpoints in their regions in the shortest possible time.

GTM allows users in different regions to access different IP address pools, and supports user group management and group access. This helps improve the overall user experience of the service.