How Cloud‑Native Is Reshaping China’s Game Industry and What Elastic Strategies Developers Need

Market Overview

IDC’s 2024 H1 China Game Cloud Market Report shows the market reached $910 million, a 5.9% YoY increase, with high‑end cloud services, cloud‑native products, and real‑time interactive services driving double‑digit growth. Game license approvals also rose sharply, creating a favorable environment for new releases.

Industry Shift to Cloud‑Native

After years of trial and error, deploying new games on public‑cloud architectures has become a consensus. Publishers leverage advanced cloud technologies, richer high‑level products, and easier service invocation to accelerate launch cycles, improve operational efficiency, and avoid the management challenges of hybrid setups.

Projections suggest the market will reach $2.44 billion by 2028, assuming stable regulations and continued downstream demand.

Benefits of Kubernetes for Game Services

Kubernetes provides powerful orchestration, decoupling resources from workloads, reducing operational labor, and enabling declarative self‑healing. Containers unify development and testing environments, accelerate iteration, and improve on‑line robustness, while raising resource utilization.

Case study: Lilith’s "Sword & Expedition: Journey" migrated to a cloud‑native stack, achieving 40‑60% higher hardware utilization, reducing release time from hours to minutes, and cutting ops costs by over 40%.

Elasticity Challenges for Stateful Game Servers

Game servers are stateful and cannot rely on simple web‑style auto‑scaling. Two management models exist:

Manual control (e.g., zone servers) – typically use vertical scaling.

Automatic control – further divided into:

Application‑Layer Elastic Strategy

Standard Kubernetes workloads lack business‑state awareness, and the Horizontal Pod Autoscaler (HPA) cannot target pods based on game‑specific states, limiting effective scaling.

OpenKruiseGame (OKG) introduces the GameServerSet workload, adding:

Business‑state probing via custom scripts, recorded in GameServer objects.

State‑aware termination: only pods whose opsState is WaitToBeDeleted are scaled down.

This enables precise, safe scaling without accidental player disruption.

State Model for Match‑Driven Servers

Typical states:

None – server created but not yet assigned.

Allocated – server assigned to a match, players active.

WaitToBeDeleted – match ended, server ready for removal.

Transitions are driven by match lifecycle events; optional PreDelete phase allows graceful player exit before final deletion.

Application‑Layer Scaling Workflow

Server created → state None.

Players join → state Allocated.

Match ends → state WaitToBeDeleted (or None for no‑restart policy).

For always‑on servers, additional metrics (e.g., low resource water‑mark) trigger scaling decisions, combined with custom ServiceQuality hooks to prevent new player assignments to servers slated for removal.

Resource‑Layer Elastic Options

Two compute provisioning models are used:

ECI Serverless – delivered via Alibaba Cloud Container Service (ACS) for lightweight, short‑lived games.

ECS Nodes – managed through ACK elastic node pools for heavyweight titles (MMORPG, MOBA, etc.).

For high‑state games, additional considerations include:

Host networking to reduce latency and avoid NAT overhead.

Pre‑scale‑down log collection via DaemonSet to preserve diagnostics.

Alibaba Cloud’s “instant elastic” node pool provides fast cold‑start (<45 s for 10k cores), one‑click configuration, and deterministic capacity planning.

Conclusion

Cloud‑native adoption and state‑aware elasticity are becoming indispensable for Chinese game developers. Leveraging Kubernetes, OpenKruiseGame, and Alibaba Cloud’s elastic resources enables developers to handle traffic spikes, lower costs, and deliver smoother player experiences, positioning the industry for continued growth through 2025 and beyond.