Cloud Native 24 min read

Didi Internationalization Site Building: Application Modeling and Cloud‑Native Delivery Framework

Didi’s international travel platform created an application‑centric, cloud‑native delivery framework that uses an OAM‑based model, KubeVela, and CUE to standardize workload descriptions, automate multi‑cloud deployment, integrate with CI/CD pipelines, and dramatically improve planning, delivery, and refactoring efficiency.

Didi Tech
Didi Tech
Didi Tech
Didi Internationalization Site Building: Application Modeling and Cloud‑Native Delivery Framework

Background: Didi's international travel platform shares experiences on improving data‑center construction efficiency through three aspects—efficiency in planning, delivery, and refactoring—aiming to build an application‑centric automated delivery framework.

Goal analysis: The overall goal is to establish a standardized management model describing all workloads of an application, enabling standardized and high‑efficiency delivery in hybrid‑cloud environments.

Application model: Emphasizes separation of concerns among infrastructure, development, and operations teams; requires a platform‑agnostic, highly extensible model that can describe compute, storage, middleware, and operational features, supporting multi‑cloud deployment.

Delivery framework: Automates delivery processes for diverse dependencies, ensuring correct ordering and providing a highly extensible integration method that abstracts underlying platforms.

Solution ideas & challenges: Proposes a standardized application description based on the OAM model, managing the full lifecycle of dependencies, handling resource lifecycle, and addressing challenges such as template flexibility, resource association, and configuration changes.

Technical implementation: Uses OAM to define components (business‑focused) and traits (operations‑focused), builds an OAM‑based application description, and adopts KubeVela (an OAM‑compliant cloud‑native delivery platform) with CUE language for extensible modules.

Component abstraction & UI standardization: Introduces a component market where services (e.g., MySQL, Redis) publish definitions; UI‑Schema is generated dynamically to render configuration forms, supporting fixed, dynamic, and automatically generated values.

Delivery engine & workflow: Integrates the delivery engine into existing CI/CD pipelines, defines stages and tasks, and provides a customizable workflow that can orchestrate arbitrary dependency ordering, conditional logic, and status monitoring.

Observability & status management: Chooses a polling‑based approach to monitor component delivery status, leveraging KubeVela’s declarative reconciliation to keep the workflow up‑to‑date.

Summary & outlook: The application center has significantly improved delivery efficiency for Didi’s international travel services, and future work will focus on finer‑grained workload management and multi‑active data synchronization.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

KubeVelaOAMApplication DeliveryInfrastructure Automation
Didi Tech
Written by

Didi Tech

Official Didi technology account

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.