Baidu AI Cloud Financial Services China Translated from Chinese

Industrial and Commercial Bank of China

Application Refactoring · System Migration

ICBC needed a faster, more elastic cloud architecture for digital banking workloads because its original serverless platform could not keep up with application growth, model release needs, and the bank's broader push toward cloud-native modernization.

Model release speed improved 10x.
Resource utilization improved 80%.

Reported impact

Business outcome

ICBC improved elasticity, lowered infrastructure overhead, accelerated application and model delivery, and created a financial-grade cloud-native reference architecture for broader enterprise modernization.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

ICBC rebuilt its financial-grade cloud platform around Baidu AI Cloud's Tianhe Stack and Function Compute to create a Serverless 2.0 architecture. The bank integrated the new function-computing core with its existing distributed systems and cloud platform, then used it to support BFF aggregation, server-side rendering, static assets, batch processing, database-update jobs, and rapid model publishing. Function Workflow lets teams compose larger batch tasks from individual functions, while Kafka-triggered execution and direct node connections support operational jobs that spike during peak release periods. By wrapping formerly heavyweight services in function-based interfaces, the bank avoided extra load-balancer deployments, improved elasticity, and gave project managers a faster path to put trained models such as investment backtesting into production. The platform is positioned as a supplement to microservices, helping ICBC modernize applications and lift resource efficiency without abandoning its broader distributed architecture.

Data flow

Business requests from mini programs, H5, and other banking services are routed into function-based BFF, SSR, and static-resource components on the serverless platform. Batch and model-release jobs are triggered through workflows and Kafka events, and the resulting services or outputs are published back into ICBC's distributed banking environment for production use.

Solution architecture

5 components · 4 layers
  1. Ingest
    • Kafka Trigger Starts function-based jobs from event streams and supports peak production operations such as model publishing and database updates.
  2. Compute
    • Function Compute Supplies the core serverless execution engine for application, batch, and model-serving workloads.
  3. Serving
    • Serverless 2.0 Platform Packages the bank's upgraded function-based architecture and connects it to existing distributed systems.
  4. Orchestration
    • Tianhe Stack Cloud-Native Private Cloud Platform Provides the private-cloud foundation that underpins ICBC's financial-grade serverless architecture.
    • Function Workflow Combines multiple function steps into larger batch-processing flows for jobs such as text verification.

Architecture clues

  • Function Workflow and Kafka-triggered execution were used to orchestrate larger banking batch processes.
  • ICBC treats serverless as a complement to microservices rather than a full replacement.
  • The platform supports BFF aggregation, server-side rendering, static resources, batch jobs, database updates, and model release on the same serverless base.

Evidence from the source

Application scenarios include BFF services, SSR, static resources, batch jobs, database updates, and model publishing (original: 主要包括BFF接口聚合服务、服务端渲染SSR、静态资源服务…批量任务…数据库安装场景…第三个场景是模型发布).
ICBC built a Serverless 2.0 architecture around Baidu's function-computing product on Tianhe Stack (original: 工商银行以百度智能云天合Stack的函数计算产品为核心打造了Serverless 函数计算平台技术架构2.0).
Migrating fund-combination backtesting models to function compute supports frequent and rapid releases (original: 通过将基金组合回测模型迁移到函数计算平台…需要频繁且快速的模型发布).
The platform integrates with ICBC's existing distributed and cloud-computing technology systems and provides a complete function engine, management, and delivery capability (original: 并与工商银行现有的分布式、云计算技术平台做对接,为应用提供完整的函数核心引擎、函数管理能力、开发交付能力).
The project improved model release speed by 10x and resource utilization by 80% (original: 模型发布速度提升10倍;资源利用率提升80%).
Transparency Evidence & methodology 100/100 reference value · 89% 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 value100/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 impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 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. Baidu AI Cloud

    Industrial and Commercial Bank of China customer story

    First-party
    https://cloud.baidu.com/customer/case/icbc.html
    Source type
    Vendor-published customer story
    Published
    May 6, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page May 6, 2025 · Baidu AI Cloud · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.