How Serverless Transformed Front-End Development in Alibaba’s Waou Video Project

2019 Serverless R&D Mode Upgrade: Waou Video Case Study

In early 2019, Alibaba's Taobao technology team launched a Serverless R&D mode upgrade plan, with Waou Video as the first business to adopt it. This talk shares the story of the past six months, exploring what Serverless means for front‑end developers and the benefits gained.

Share Content

Business Landing

From Zero to One

Future Choices

Business Landing

Waou Video is a short‑video shopping feature on the Taobao homepage.

"Three‑High" Business

High traffic

High stability requirements

High iteration frequency

High traffic brings high stability demands, and as a shopping guide, the iteration frequency is also very high.

Development Pain Points

During a year of development, several pain points emerged, especially long integration periods that often exceeded ten days.

The business follows a strong mid‑platform strategy, and the shopping guide is in a rapid‑iteration phase, leading to many development challenges.

Integration

Integration consumes about 30% of development cost, causing fatigue and slowing iteration.

Monotonous Business Development

Daily work often involves repetitive data fetching and API calls.

Front‑End Resource‑ization

Front‑end developers focus on UI and interaction, lacking deep business logic exposure, which limits growth.

R&D Mode Upgrade Campaign

In April 2019, the front‑end team started the upgrade campaign. By taking responsibility for both front‑end and back‑end using JavaScript, communication and integration costs were greatly reduced, meeting the fast‑iteration needs.

Single person handles front‑end and back‑end with JS, reducing communication cost.

Being close to users lowers business communication cost.

Front‑end developers gain opportunities to upgrade their capabilities.

Back‑end engineers can focus on new challenges.

Business Migration

The back‑end is stateless and of moderate complexity, making it suitable for Serverless. Migration requirements were:

No extra time for technical changes; deliver on schedule.

Zero impact on online service.

Back‑end handover should not affect future development.

After migration, development time per iteration increased slightly (from 10 to 12 days) but required one fewer person, resulting in cost savings.

From Zero to One

The migration process includes four stages: requirement acquisition, local development, deployment & invocation, and operations.

Requirement acquisition: review, technical review, development, release, and summary.

Local development: function development, service call, unit test, function release.

Deployment & invocation: Node FaaS functions are packaged and deployed.

Operations: monitoring, tracing, and alerting.

Multi‑Function Directory Structure

Traditional FaaS projects isolate each function, causing duplication. A new shared‑dependency structure was introduced to improve developer efficiency.

Clean Architecture Exploration

Adopting clean architecture with IoC and dependency inversion reduced iteration difficulty.

Service Marketplace – HSF One‑Stop Solution

Provides end‑to‑end HSF service call and testing support.

Unit Testing

Both Mocha and Jest are supported, and FaaS functions are integrated into the CI system.

Error Handling

Error grading: ignore / warning / critical.

Custom error names for quick identification.

Attach key information for each error.

Java Fallback

If a Node request fails, a Java fallback ensures service continuity.

Release Process

A one‑stop development platform manages function versioning and rollback.

Debugging Closed Loop

Sandbox provides remote debugging in pre‑release environments.

Function Monitoring

Sandbox offers a full‑stack Node.js governance platform with metrics, tracing, alerts, and white‑screen logs.

Operations Data

Provides clear runtime data for each function.

Link Analysis

Full‑link analysis helps locate issues quickly.

White‑Screen Logs

Real‑time logs give insight into function behavior.

Alerting

Custom alerts notify via SMS, phone, etc., enabling rapid fault resolution.

FaaS Business Capability

FaaS function tools are complete; building business feels like stacking blocks!

Teams are encouraged to adopt FaaS for relevant business needs.

Future Choices

After six months of migration, the author reflects on the experience and the question: "Can R&D mode upgrade help the business win first?"

R&D Mode Upgrade Inference

Because we use Serverless.

Therefore front‑end capabilities are upgraded.

Result: Business gains a competitive edge.

Story: Technology Changes Life

Technology now lets us solve problems instantly with a phone, but outcomes can still vary.

Personal Choices

Faced with two options—remain a pure tool or become a business partner—the author chose to become a partner to test whether the R&D upgrade truly benefits the business.

Business Dialogue

After studying relevant articles, the author engaged with product managers, participated in user research, and discovered gaps in business understanding.

Example: Integrating Taobao Push

By adding Taobao Push messaging, Waou Video increased daily UV by over 20%.

Conclusion: Changes Brought by FaaS to Front‑End

A colleague commented that FaaS makes development feel like building with blocks, and the author aims to continue exploring how Serverless can help the business win.

We must not forget why we started, even as we move forward.