Alibaba Cloud Financial Services China Translated from Chinese

Shuhe Technology (数禾科技)

Risk Management

Shuhe Technology had to run growing numbers of online risk models for pricing, limits, and loan-term decisions, but the infrastructure under those services could not scale fast enough with request volume. As inference services multiplied, resource waste and version-management pain increased, driving up both model-serving cost and maintenance effort.

all new models now deploy online through ACK+Knative
model-serving cost reduced about 60%

Reported impact

Business outcome

Shuhe improved the stability of model services under bursty financial traffic and reduced the cost of running them at scale. It also standardized future model releases on the same serverless deployment pattern, making gradual releases and multi-version coexistence normal parts of the risk-model lifecycle.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

Shuhe Technology moved its online risk-model services to an ACK plus Knative deployment model so serving capacity could track request demand instead of staying fixed. Knative gave the team request-based auto-scaling, scale-to-zero behavior for idle services, and built-in multi-version management for gradual rollouts or side-by-side model releases. Because Shuhe already ran on Alibaba Cloud infrastructure, the integrated ACK packaging of Knative shortened deployment and debugging time and let the team introduce serverless model serving without reworking its whole platform. After launch, the company also refactored its internal model-delivery pipeline so new models are published through the same ACK+Knative path, which standardizes online deployment while keeping operating cost predictable. This turned risk-model serving into an elastic cloud-native platform rather than a growing collection of static services.

Data flow

Risk-management workloads send scoring requests to model services deployed on ACK+Knative, where capacity scales with live demand and different model versions can serve traffic concurrently. Deployment pipelines publish new models into the same serving path so updated scores flow back into credit limits, pricing, and term decisions without manual infrastructure changes.

Solution architecture

2 components · 2 layers
  1. Compute
    • Elastic Container Instance (ECI) Provides elastic container capacity around the serverless model-serving deployment.
  2. Orchestration
    • ACK Serverless Knative Hosts Shuhe's online risk-model services with request-based scaling, scale-to-zero, and multi-version delivery.

Architecture clues

  • Model-serving capacity is driven by request demand rather than static machine allocation.
  • Shuhe uses Knative's multi-version management to support coexistence and gray releases for online risk models.
  • The deployment model is integrated into the internal model-release pipeline so future services inherit the same serverless controls.

Evidence from the source

After launch, Shuhe reported a roughly 60% cost saving and said all new models are now deployed online through the ACK+Knative pipeline. (original: 资源的使用效率也获得了显著提高,节约成本约 60%... 目前数禾的所有新增模型均已通过 ACK+Knative 方式部署在线上提供服务。)
It adopted ACK+Knative so model services could scale by request, shrink to zero when idle, and support multi-version model delivery. (original: 基于 Knative 的 Serverless 服务方案,实现了根据请求的扩缩容能力、允许 Pod 缩容到 0 的冷启动能力以及多版本的管理能力。)
Shuhe said risk management required large batch and model computations for limit, pricing, and term adjustments, but underlying resources could not flex with request volume. (original: 在风险管理业务中... 包括用户额度、定价、可借期限... 支撑模型计算的底层应用资源无法灵活且快速地根据请求量来智能化调整机器资源支持运算能力。)
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

    数禾科技 AI 模型服务基于阿里云容器服务实现 Serverless 容器化

    First-party
    https://www.aliyun.com/customer-stories/financial-services-2024-shuhegroup-serverless
    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 Dec 8, 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.