Alibaba Cloud Media and Entertainment Global Translated from Chinese

XD / TapTap (心动 / TapTap)

IT Operations Automation · Marketing Personalization

TapTap's ad-driven recommendation, search, and content workflows depended on machine-learning models and NLP processing, but the older ECS-plus-Rundeck environment made deployments and service management too slow and expensive. The team needed a more elastic platform for automated model updates, experiment tracking, content parsing, and online estimation services while continuing to support Go-based services and fast release cycles for a globally used game community.

38 games operated as of mid-2022
50 million monthly active users
minute-level releases
second-level elastic scaling

Reported impact

Business outcome

TapTap gave its algorithm engineers a faster, lower-ops platform for model deployment, NLP enrichment, and online estimation. The serverless design let the company decouple triggering logic from business code, reduce infrastructure management, and support faster releases and elastic scaling for recommendation and advertising services that affect user experience and monetization.

  • Cost Reduction
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

XD moved TapTap's algorithm platform toward an all-on-serverless design using Function Compute (FC) and Serverless Application Engine (SAE). Model artifacts exported into OSS buckets trigger FC deployment workflows, so TensorFlow, PyTorch, and similar models can be published without separate engineering handoffs. An internal experiment-management service also runs on FC with HTTP triggers, recording training parameters and log addresses so model experiments stay traceable. New user posts are pushed through Kafka to an NLP parsing service, where event-driven execution invokes analysis only when content arrives and stores the results for later search use. The team also schedules FC jobs to pull unstructured billing data and aggregate MaxCompute and EAS consumption by task and model. On the serving side, SAE hosts shared estimation services used by search, recommendation, and advertising workloads, giving TapTap faster releases, microservice support, and lower operations overhead.

Data flow

Model artifacts are written to OSS and trigger FC-based deployment jobs, experiment submissions arrive through HTTP-triggered FC services that log parameters and log locations, and new user posts are pushed through Kafka into event-driven NLP analysis for search indexing. Processed signals and online prediction services are then served through SAE, while scheduled FC tasks aggregate MaxCompute and EAS consumption data for internal cost control.

Solution architecture

6 components · 4 layers
  1. Ingest
    • Kafka Streams newly created content into the NLP parsing workflow for downstream search enrichment.
  2. Compute
    • Function Compute (FC) Runs TapTap's event-driven model deployment, experiment-management, NLP parsing, and scheduled cost-statistics workflows.
    • Serverless Application Engine (SAE) Hosts the online estimation and microservice layer shared across search, recommendation, and advertising workloads.
  3. Storage
    • Object Storage Service (OSS) Stores exported model artifacts whose arrival triggers automated deployment and update jobs.
    • MaxCompute Provides a source for scheduled resource-consumption analysis tied to model and task cost management.
  4. Serving
    • Elastic Algorithm Service (EAS) Supplies algorithm-service resource signals that are aggregated for model-cost monitoring and management.

Architecture clues

  • Kafka-triggered NLP analysis is invoked per new post so the platform can align cost with content volume.
  • OSS-triggered model deployment lets algorithm engineers publish models without a separate manual deployment path.
  • SAE is used for shared estimation services that support search, recommendation, and advertising scenarios.
  • Scheduled FC jobs aggregate MaxCompute and EAS resource usage by task and model to improve cost transparency.

Evidence from the source

New posts are pushed through Kafka to NLP processing for later search use, and SAE gave TapTap minute-level releases plus second-level elastic scaling. (original: 当 TapTap 站内的用户发了一个新的帖子,会通过 Kafka 推送到 NLP 分析服务商进行 NLP 的处理与解析,存下来用于之后的搜索……不停机发布 + 分钟级上线……秒级弹性缩扩容。)
TapTap said its serverless work was driven by algorithm scenarios such as deep-learning-model updates and deployment, model-experiment records, and NLP analysis for new in-platform content. (original: 搜广推都依赖的深度学习模型自动化更新/部署,以及组内算法工程师都需要依赖的模型实验记录平台,还有站内新内容的一些 NLP 分析处理等。)
The team chose a Serverless architecture built from SAE and Function Compute because it could cover most business scenarios with lower operations cost than ECS plus self-built Kubernetes. (original: 心动技术团队选择了……Serverless 架构,使用 Serveless 应用引擎(SAE)和函数计算 FC……可以覆盖掉 TapTap 绝大多数的业务场景,实现所有应用服务 All On Serverless。)
When model files are exported to an OSS bucket, TapTap automatically triggers deployment and update services so algorithm engineers can publish models without depending on extra engineering staff. (original: 算法工程师在训练完自己的模型……只需要导出到指定的 OSS 存储空间 Bucket,就会触发模型的更新与部署服务。这样算法工程师在不依赖其他工程人力的情况下也能执行模型的部署、更新以及后续的弹性缩扩容。)
Transparency Evidence & methodology 75/100 reference value · 93% 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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence93%
  • 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 evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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

    心动 TapTap 算法平台的 Serverless 探索之路

    First-party
    https://www.aliyun.com/customer-stories/internet-and-info-tech-2022-xd
    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 May 7, 2025 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.