Alibaba Cloud Media and Entertainment China Translated from Chinese

Rokid

Application Refactoring

Rokid needed a better way to run GPU-intensive AR guidance services for digital-culture experiences. The company wanted demand-based GPU elasticity, faster release and rollback, better control of burst capacity, and a standard serverless pattern that could support real-time scene-experience services without a maze of Kubernetes objects and manual tuning.

AHPA plans capacity across 1440 minutes per day
products are used in 80+ countries and regions

Reported impact

Business outcome

Rokid improved rollout speed and demand responsiveness for AI-backed AR services while keeping GPU use closer to actual traffic. The company can now gray-release or roll back versions more easily, respond to burst demand with mixed ECS and ECI capacity, and run the online service layer on a more standard cloud-native serverless pattern.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

Rokid used Alibaba Cloud ACK with Knative to serverless-ize the online service layer behind its AR exhibition-guidance applications. Knative gives the team request- and concurrency-based scaling, traffic-based gray release, rollback, and multi-version management so new application versions can ship without rebuilding a large set of Kubernetes primitives for each rollout. To reduce the lag of conventional HPA scaling, Rokid also adopted ACK's AHPA prediction so pods can be prepared ahead of expected traffic increases rather than only after metrics cross a static threshold. The deployment mixes ECS and ECI capacity and applies a custom ResourcePolicy so normal load prefers long-lived ECS capacity while burst traffic spills into ECI, and scale-down releases ECI first. Together, those controls let Rokid pursue GPU efficiency, faster delivery, and more deterministic real-time service behavior for AR scene experiences.

Data flow

AR scene-experience requests enter Knative services on ACK, where traffic levels drive scaling and version-routing behavior. AHPA predicts capacity needs ahead of spikes, while ResourcePolicy determines whether workloads land on ECS or ECI resources before responses are returned to location-aware AR clients.

Solution architecture

4 components · 3 layers
  1. Compute
    • Elastic Container Instance (ECI) Supplies burst container capacity when request spikes exceed baseline resources.
  2. Orchestration
    • Container Service for Kubernetes (ACK) Hosts the serverless AI application environment that runs Rokid's online AR services.
    • Knative Adds request-driven scaling, multi-version delivery, and traffic-based rollout controls for GPU-backed services.
  3. Governance
    • AHPA Predicts upcoming demand and pre-scales pods before traffic surges hit the service.

Architecture clues

  • AHPA is layered on top of Knative to pre-warm capacity before forecast traffic spikes arrive.
  • ResourcePolicy makes ECS the preferred baseline and ECI the burst tier so scale-in behavior remains deterministic.
  • Rokid uses request and concurrency signals, not raw GPU-utilization thresholds, as the main elasticity trigger for online AI services.

Evidence from the source

ACK AHPA learns from historical ready times and metrics so pods can be expanded before traffic rises, addressing elasticity lag. (original: AHPA... 可以根据历史 Pod 的 Ready Time 以及历史 Metrics 自动学习规律,在业务量上涨之前的一个 Ready Time 开始扩容。)
Rokid said the real-time scene-experience business depended heavily on GPUs and needed both on-demand elasticity and second-level startup efficiency. (original: Rokid 尤为关注 GPU 资源的依赖性... 核心问题聚焦于以下两点:成本效益(按需弹性伸缩) 启动效率(实现秒级启动)。)
The company adopted ACK + Knative so services could scale on request or concurrency, support gray release and rollback, and mix ECS and ECI for cost and stability. (original: Rokid 选择了阿里云 ACK + Knative 的解决方案... 提供了基于请求数、并发等指标的自动弹性能力,并且通过多版本管理机制,可以方便地实现基于流量的灰度发布、快速回滚... 常态业务下使用 ECS 资源,在有突发业务流量的时候,通过 ECI 按需提供资源。)
Transparency Evidence & methodology 90/100 reference value · 88% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence88%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Alibaba Cloud

    Rokid借助Knative实现AI应用Serverless化_人工智能与AI_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/ai-2024-rokid-ack
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Published on source page Aug 22, 2024 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.