Alibaba Cloud Financial Services China Translated from Chinese

WeTech (微财)

Risk Management

WeTech relies on large-scale user data to evaluate lending risk, but as its business expanded, big-data model training became a bottleneck. The company needed a mature and reliable data-science platform that could break through single-machine training limits, improve training efficiency, and avoid the staffing and maintenance burden of building a full-featured model-training environment from scratch.

Fusion engine performance improved more than 3x versus open source
all big-data compute tasks were migrated in about 1 month
resource provisioning reached second-level speed

Reported impact

Business outcome

WeTech replaced a heavier self-managed training approach with a managed lakehouse training stack that could scale with the business. The new platform delivered more than 3x engine performance versus the open-source baseline, second-level resource provisioning, and a complete migration of all big-data compute tasks to the cloud in roughly one month, while reducing overall storage and operations costs.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

WeTech standardized its machine-learning platform on Alibaba Cloud EMR Serverless Spark and OSS. Instead of managing long-lived compute clusters, the team uses the serverless Spark service as a unified execution layer for data processing, analysis, and machine-learning jobs, taking advantage of the Fusion engine, vectorized execution, and RSS enhancements to improve performance over open-source Spark. The platform is tightly integrated with the broader lakehouse environment: dw-shell handles data collection, Apache Paimon provides the lake storage format, and Spark, Flink, and Hive are combined to form a full data-lake ecosystem for training and monitoring scenarios. By using compute-storage separation with OSS and task-level elastic provisioning, WeTech can run large-scale risk-model training with much lower infrastructure overhead while still giving data scientists familiar Python, SQL, PySpark, notebook, and scheduling workflows.

Data flow

Collected lending and user-behavior data is gathered through WeTech's ingestion tooling into the lakehouse, stored through OSS and Paimon, and then processed by EMR Serverless Spark for feature preparation, model training, and analytical jobs. The resulting models and datasets are used by WeTech's financial risk-evaluation workflows and related real-time monitoring or analysis scenarios.

Solution architecture

3 components · 2 layers
  1. Compute
    • EMR Serverless Spark Provides the managed compute layer for data processing, analysis, and machine-learning training jobs.
  2. Storage
    • Object Storage Service (OSS) Supplies the decoupled storage layer that lowers cluster cost and supports the lakehouse architecture.
    • Apache Paimon Acts as the data-lake storage framework used with Spark, Flink, and Hive for WeTech's data platform.

Architecture clues

  • Apache Paimon, Spark, Flink, and Hive are combined into a unified lakehouse ecosystem.
  • Built-in SQL editor and notebook tooling let data scientists work in the same managed environment as ETL developers.
  • The platform is built with compute-storage separation, with OSS as the storage substrate and Serverless Spark as the elastic compute tier.
  • WeTech uses one serverless Spark layer to cover data processing, analytics, and machine-learning jobs rather than separate engines for each.

Evidence from the source

For lake storage, WeTech adopted Apache Paimon and combined it with Spark, Flink, and Hive to form a complete data-lake ecosystem that already supports real-time monitoring and analysis scenarios. (original: 在数据入湖方面,微财采用了 Apache Paimon 作为数据湖存储框架,并集成了 Apache Spark、Flink 和 Hive 作为计算引擎,构建了一个完整的数据湖生态系统。)
In the machine-learning scenario, the two core problems were breaking through single-machine training limits and improving training efficiency. (original: 在机器学习场景下需要解决的问题如下:一是要突破单机训练使用的数据规模的瓶颈。二是要提高训练的效率。)
WeTech chose EMR Serverless Spark because the managed platform unified data engineering and data science, and its Fusion engine, vectorized execution, and RSS capabilities stood out in evaluation. (original: 微财最终选择了阿里云 EMR Serverless Spark。作为一站式全托管湖仓分析平台,其自研 Fusion 引擎,内置高性能向量化计算和 RSS 能力,统一的数据工程和数据科学等,都是微财决定选择 Serverless Spark 的重要原因。)
WeTech depends on big data to evaluate risk during the lending process, and the growing scale of its datasets made model training a bottleneck. (original: 微财依托大数据评估用户借款过程中的风险,随着微财业务的快速发展,积累了大量用户数据,大数据集的训练逐渐成为瓶颈。)
Transparency Evidence & methodology 90/100 reference value · 95% confidence · 2 sources

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
    2 source references 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

    阿里云 EMR Serverless Spark 在微财机器学习场景下的应用

    First-party
    https://www.aliyun.com/customer-stories/financial-services-2025-wetech
    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
  2. Aiqicha

    北京微财科技有限公司

    Independent secondary
    https://aiqicha.baidu.com/details/ugknowledge?id=99b3492a38c1b4496fb63e4564780dfa

    The page content states the company is 属小型企业(2024年参保人数33人); the standard mapping classifies fewer than 250 employees as SMB.

    Source type
    Government-derived company profile
    Supports
    • Company size

Date evidence

  • Published on source page Feb 13, 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.