Overview of Global Acceleration Products and Deployment Scenarios

1. Global Acceleration Product Categories & Current Cloud Vendor Support

The following table summarizes the availability of acceleration channels, Anycast, and global network features for major cloud providers:

Accelerator Type

Cloud Vendor

Acceleration Channel

Anycast

Global Network

Tencent Cloud

√

√ (pending test)

×

Alibaba Cloud

√

√ (pending test)

×

AWS

×

√

×

Google Cloud

×

√

√

2. Business Scenarios and Generic Solutions

① Acceleration Channel

Cloud vendors: Tencent Cloud & Alibaba Cloud

Applicable scenario: Services with a unified gateway or external port for a small number of services.

Advantages:

Highly targeted acceleration for specific regions; can combine with AWS Route 53 for region‑based DNS resolution.

Disadvantages:

Multi‑region DNS changes are cumbersome.

Channel cost is relatively high.

Example game: "Zhicheng War Chronicle" using Tencent Cloud GAAP acceleration channel.

Architecture diagram:

② Anycast

Cloud vendors: AWS & Google Cloud

Applicable scenario: Services with a unified gateway or external port for a small number of services.

Advantages:

Simple configuration.

Relatively low cost.

Disadvantages:

Lacks targeting; depends on Anycast stability.

Architecture diagram:

Representative games: "Apocalypse Noise" (AWS) and "Ant Legion" (Google Cloud).

Architecture diagram:

Tip: Anycast IP load balancers limit ports, so they cannot handle all ports.

③ Global Network (Premium Network)

Cloud vendor: Google Cloud

Applicable scenario: Services without a gateway, where game servers are directly exposed to the internet.

Advantages:

No configuration required; directly reachable by global players.

Leverages the provider’s backbone network, offering strong DDoS resistance.

Disadvantages:

Reliant on Google’s backbone and POP node stability.

3. Obtaining the Client’s Real IP

The table below lists the protocols used by each cloud vendor at Layer 4 and Layer 7 to expose the client’s original IP address.

Cloud Vendor

Protocol

Tencent Cloud

Alibaba Cloud

AWS

Google Cloud

Layer 4

TOA module

Direct pass‑through (requires console configuration)

Direct pass‑through to EC2 origin (no extra setup)

1. go‑mmproxy 2. proxy‑protocol

Layer 7

X-Forwarded-For , includes the original client IP

X-Forwarded-For , includes the original client IP

X-Forwarded-For , includes the original client IP

X-Forwarded-For , includes the original client IP

Tips:

When the traffic flow is User → Global Acceleration → Layer 4 Load Balancer → Backend Application , the backend cannot obtain the client’s real IP.

When the flow is User → Global Acceleration → Layer 7 Load Balancer → Backend Application , the backend can retrieve the real source IP via the X‑Forwarded‑For header.