Alibaba Cloud Software / SaaS China Translated from Chinese

G-Town (海牙湾)

Marketing Personalization · Supply Chain Optimization

G-Town was scaling an AI-driven digital platform used for customer-lifecycle experience and supply-chain decision support, but the older ECS-based architecture wasted resources, could not react quickly enough to short traffic surges, and required manual, error-prone deployments. The company also lacked consistent observability and needed a safer release model for continuously changing business services.

CPU utilization rose from below 20% to above 50%
application startup time improved by more than 30%
cost savings exceeded 60%
iteration speed improved 3x

Reported impact

Business outcome

G-Town completed a full architecture upgrade in two months and gave its AI digital platform a more elastic and controllable runtime. Resource utilization rose, idle spend fell, releases sped up from hours to minutes, and the team improved stability for bursty business events. The serverless stack also made it easier to keep iterating on digital services tied to customer-lifecycle optimization and supply-chain decision support.

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

Solution

G-Town rebuilt the runtime for its AI digital platform on Alibaba Cloud around Serverless Application Engine (SAE) and the cloud-native API gateway so services could scale and release faster without heavy infrastructure management. Business services are deployed to SAE, where load-driven scaling handles short peaks and can shrink idle workloads to one instance, while CPU Burst and Dragonwell JDK reduce Java startup overhead. The CI/CD pipeline was refactored around kubectl-sae, YAML-defined service specs, and one-click deployments so packaging, upload, rollback, and gray rollout could be automated instead of managed node by node. In front of those services, the MSE gateway provides routing, security controls, rate limiting, and gray-release policy management, while monitoring and log services improve diagnosis. The result is a serverless application platform that underpins G-Town's machine-learning-driven digital services while reducing operational drag.

Data flow

Business requests for G-Town's AI digital platform enter through the MSE gateway, which applies routing and traffic policies before sending them to SAE-hosted application services. SAE scales those services according to load, while monitoring signals and logs flow into Alibaba Cloud observability services so releases, incidents, and high-traffic events can be diagnosed and tuned more quickly.

Solution architecture

4 components · 4 layers
  1. Compute
    • Serverless Application Engine (SAE) Runs G-Town's AI-platform application services with automatic scaling, release controls, and high-availability support.
  2. Storage
    • Log Service Centralizes operational logs that support troubleshooting and service analysis across the serverless environment.
  3. Serving
    • Cloud-native API Gateway (MSE Gateway) Handles routing, security policy, and gray-release traffic management in front of the platform services.
  4. Governance
    • Application Real-Time Monitoring Service Provides integrated runtime visibility so the team can identify faults and performance issues quickly.

Architecture clues

  • MSE gateway is used for routing, DDoS protection, rate limiting, and gray-release traffic control in front of business services.
  • SAE can shrink workloads to one instance during low-traffic periods and use CPU Burst during startup spikes.
  • The source describes the application platform in detail but does not disclose the internal model stack behind G-Town's AI services.
  • kubectl-sae plus YAML-defined service specs is part of the production release path for JAR applications.

Evidence from the source

After the migration, cost savings exceeded 60%, overall work efficiency improved 40%, iteration speed improved 3 times, and system stability rose from 99.5% to 99.99%. (original: 成本节约超 60%……整体工作效率提升 40%……迭代速度提升 3 倍……系统稳定性从 99.5% 提升至 99.99%。)
G-Town moved to SAE and the cloud-native API gateway so services could scale automatically, release with canary and full-link gray strategies, and recover quickly across availability zones. (original: SAE 支持根据业务负载自动调整实例数量……SAE 通过分批发布、金丝雀发布和全链路灰度发布……SAE 天然支持多可用区部署和同可用区亲和特性。)
G-Town said it is building a next-generation AI digital platform that uses intelligent algorithms and machine learning to improve full-lifecycle user experience and supply-chain decision making. (original: 公司正加速构建新一代 AI 数字化平台,通过智能算法优化和机器学习技术,持续提升用户全生命周期体验与供应链智能决策能力。)
The old ECS-based architecture had CPU utilization below 20%, poor elasticity for 1-2 hour peaks, and manual node-by-node release work. (original: 部分服务器 CPU 利用率长期低于 20%……传统云主机架构难以应对业务流量的波峰波谷(高峰期仅持续 1-2 小时)……应用发版需根据 ECS 服务器应用负载情况逐一分发。)
Transparency Evidence & methodology 100/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 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
    6 metrics 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

    阿里云Serverless助力海牙湾构建智能化 AI 数字化平台_互联网&信息技术_阿里云客户案例

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