How DEF’s Frontend Platform Evolves to Overcome Monolithic Challenges

Background

DEF engineering platform was launched in July 2018, upgrading the previous Taobao release‑process engine. After three years it now serves most front‑end development and deployment processes across Taobao and the Alibaba group, but faces growing business challenges.

Platform Development

From an internal perspective the platform has become a "monolithic" application, causing rising costs for product development, maintenance, and stability. Single‑scenario demands often involve high complexity and development cost, hindering platform growth.

Environmental Changes

Externally, rapid changes in technology and business chains mean front‑end engineers must first master business release workflows (creating projects, integrating with DEF, developing, releasing, then managing versions) and then understand framework specifics, preview/debug tools, and interface testing.

Existing Challenges

Three roles—DEF side, platform side, and front‑end developers—experience contradictions. DEF can only support generic scenarios, making vertical customizations costly. Platform side relies on DEF’s open capabilities, incurring high integration costs. Front‑end developers often resort to sub‑optimal "usable" chains, limiting experience and efficiency.

Solution Idea

From a macro view, the goal is to address current problems while preparing the front‑end team for the next three years of development.

Infrastructure Improvement

With low‑code and engineering capabilities maturing, platform construction costs and thresholds drop, enabling better operation experience, development efficiency, and quality assurance.

Role Changes

The platform can be divided into three layers, analogous to cloud computing:

SAAS: primary service model providing front‑end development workflow as a product.

PAAS: open platform acting as a gateway, offering front‑end engineering services via APIs.

IAAS: self‑built container clusters for task scheduling, workflow engines, and supporting higher‑level platforms.

Vertical Platform Construction

Serverless functions are built as a separate platform using micro‑frontend assembly, improving stability and collaborative development across platform, DEF, and users.

Micro Platform Open System Solution

The system is organized into multiple layers:

Specification Layer

Standardizes core front‑end engineering processes (application, iteration, change, release) to ensure long‑term stability.

Platform Capability Layer

Enhances engineering capabilities such as tenant isolation, demand management, and performance metrics.

BAAS Capability

Addresses DEF‑open platform issues by providing versioning, rate limiting, circuit breaking, and stable API governance using POP gateway technology and client SDKs.

UI Capability Layer

Offers UI components that package engineering capabilities, reducing integration cost and enabling customizable parameters for rapid development.

Developer System Layer

Combines tools and capabilities to solve point‑ and line‑level problems, facilitating efficient composition and customization.

Business Scenario Layer

Supports various scenarios such as PHA, mini‑programs, tnpm, merchant development, and industry‑specific pipelines, delivering tailored engineering solutions.

Facing Problems

After modularizing platforms, inter‑platform connections become fragmented, creating isolated islands that increase switching costs for developers. Solutions include unified navigation, search, and SPI‑style extensions to create a seamless experience.

Summary Thinking

Front‑end engineering must maximize efficiency and quality under constraints. As business scenarios and technical capabilities evolve, the platform aims to enable one‑hour integration of open capabilities, one‑day platform setup, and one‑week rollout of development pipelines, delivering optimal developer experience.