Alibaba Cloud Software / SaaS China Translated from Chinese

Hunliji (婚礼纪)

Data Lake / Data Warehouse Modernization · IT Operations Automation

Hunliji's wedding-services platform had outgrown a self-built data warehouse. The company needed to process hundreds of millions of behavioral events per day, manage large image assets, and support marketing, order, risk-control, and payment workloads, but its earlier stack suffered from unclear lineage, inconsistent metrics, unstable scheduling, and too little automation for multi-engine data development. It also wanted an AI-assisted way to generate and optimize SQL, manage complex workflows, and improve developer productivity across a growing lakehouse estate.

annual transaction flow is at the 10-billion-plus level
manages tens of millions of bridal image assets
processes 400-500 million user-behavior log records per day
serves 20 million+ couples per year

Reported impact

Business outcome

Hunliji moved from a brittle self-built warehouse to a governed lakehouse platform that can support high-volume wedding-industry data operations and AI-assisted engineering from one environment. The redesign gave the team clearer lineage, more flexible Python and workflow execution, faster multi-engine development, and a practical Copilot layer for SQL generation, optimization, and diagnostics. That lets the platform keep supporting user insight, advertising, merchant service, and risk-control scenarios at growing scale.

  • Productivity Improvement
  • Risk Reduction
  • Scalability

Solution

Hunliji rebuilt its data estate on Alibaba Cloud around DataWorks so operational analytics and AI-assisted development could run on one governed lakehouse platform. Logs and business data are integrated through DataWorks into an OSS-HDFS data lake, where offline pipelines use Spark and Hive for layered warehouse processing while real-time streams land in Paimon through Flink. Trino and Doris provide interactive analysis for downstream users, and the new Data Studio plus workflow capabilities orchestrate multi-engine jobs, Python tasks, and lineage-aware scheduling from one control plane. The AI layer comes from DataWorks Copilot, which lets engineers generate, correct, optimize, and translate SQL or UDF logic with natural-language interaction, and also supports table discovery, table creation, and engine-parameter guidance. The result is a governed Data+AI environment that supports marketing analytics, user insight, risk monitoring, and merchant operations at production scale.

Data flow

Hunliji integrates log and business data through DataWorks into an OSS-HDFS data lake, processes offline layers with Spark and Hive, and streams real-time events through Flink into Paimon tables. Trino and Doris expose processed datasets for analysis and reporting, while DataWorks workflows orchestrate the jobs and DataWorks Copilot helps engineers generate SQL, convert code, and resolve development issues across the same governed environment.

Solution architecture

9 components · 5 layers
  1. Compute
    • Spark Runs offline transformation and layered processing jobs over large-scale platform data.
    • Hive Supports warehouse-style offline processing on top of the governed data model.
    • Flink Streams real-time data into the lakehouse so fresh operational data can be analyzed continuously.
    • Trino Provides interactive analytics over processed data for business and engineering teams.
  2. Storage
    • OSS-HDFS data lake Stores integrated log and business data for downstream offline and real-time lakehouse processing.
    • Paimon Acts as the real-time lakehouse table format for streaming data landed by Flink.
  3. Serving
    • Doris Serves processed analytical outputs for downstream decision support and operational reporting.
  4. Orchestration
    • DataWorks Provides the central development, scheduling, modeling, governance, and workflow control plane for Hunliji's enterprise data platform.
  5. Uncategorized
    • DataWorks Copilot Uses natural-language interaction to generate, optimize, convert, and troubleshoot data-development logic for engineers.

Architecture clues

  • DataWorks Copilot is used in production for SQL generation, optimization, code conversion, table discovery, and engine guidance rather than as a demo feature.
  • Hunliji uses a lakehouse pattern with offline Spark and Hive plus real-time Flink to Paimon.
  • The same DataWorks control plane handles modeling, scheduling, workflows, lineage, data quality, and AI-assisted development.

Evidence from the source

DataWorks workflows and the new Data Studio gave Hunliji automated multi-engine orchestration, while Copilot was used for SQL generation, correction, optimization, code conversion, smart table discovery, and table creation. (original: 婚礼纪使用工作流……包括编排多种大数据和 AI 引擎的数据开发节点……婚礼纪借助 DataWorks Copilot 智能助手通过自然语言交互完成更为复杂的 SQL 代码生成、优化、测试等操作……智能找表、智能建表、生成表结构。)
Hunliji said it handles 400-500 million user-behavior logs per day, tens of millions of image assets, and 10-billion-plus annual transaction flow across marketing, order, risk-control, and payment scenarios. (original: 日均处理 4-5 亿条用户行为日志……管理千万级婚纱影像资产库……年承载超百亿级交易流水,实现毫秒级优惠核销、智能商家结算及动态风控监测。)
Hunliji said the new platform would keep supporting precision marketing optimization, intelligent ad delivery, transaction risk control, and user-behavior insight while deepening Data+AI exploration. (original: 成功实现了对多源异构数据的高效汇聚与深度分析,全面赋能精准营销策略优化、智能广告投放、交易风险控制及用户行为洞察等核心业务场景。)
The company rebuilt its data platform with DataWorks, using DataWorks integration into an OSS-HDFS lake, Spark and Hive for offline layers, Flink into Paimon for real-time flows, and Trino plus Doris for interactive analysis. (original: 日志数据、业务数据通过 DataWorks 数据集成进入 OSS-HDFS 数据湖,离线链路通过 Spark、Hive 引擎根据规范的数据模型进行分层加工,实时数据通过 Flink 实时进入 Paimon 数据湖,构建湖仓一体方案,上层采用 Trino、Doris 进行交互式分析。)
Transparency Evidence & methodology 90/100 reference value · 95% 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 confidence95%
  • 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 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

    婚礼纪_计算平台客户案例_产线_DataWorks

    First-party
    https://www.aliyun.com/customer-stories/internet-and-info-tech-2025-hunliji
    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 Jun 5, 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.

Related

Similar use cases

See all like this