Cloud Native 9 min read

Containerized Page Protocol and Cloud Platform for Dynamic Traffic Pages

Xianyu introduced a containerized page protocol and cloud platform that adds a fourth Container layer to its Page‑Section‑Component model, enabling dynamic, low‑code page adjustments, traffic splitting, AB testing, and robust disaster‑recovery through multi‑level caching, thereby cutting development effort and accelerating new business page rollout.

Xianyu Technology
Xianyu Technology
Xianyu Technology
Containerized Page Protocol and Cloud Platform for Dynamic Traffic Pages

Background: Rapid growth of Xianyu’s business has led to frequent structural adjustments of traffic‑type pages (home, search, etc.) and a proliferation of similar page code across vertical services, increasing development and maintenance costs.

Solution: Introduce an end‑to‑end page‑level description protocol combined with a cloud‑based platform that enables dynamic adjustment and rendering of page structures, achieving less‑code or no‑code page modifications.

Original three‑layer protocol (Page, Section, Component): Page – contains Sections and global configs (pull‑to‑refresh, load‑more). Section – layout, init/load‑more events, and Components. Component – business‑specific, rendered by DX parser.

Extended four‑layer protocol adds a Container layer to manage multiple Pages and tabs. Container layout supports three forms: single list‑view page, pager+tab with list‑view pages, and nested containers where a sub‑container is treated as a Component with type="sub_container" and rendered by a SubContainerRenderHandler.

Client two‑side package (二方包) provides configuration fetching, traffic splitting, dynamic registration, remote calls, and disaster‑recovery mechanisms, allowing services to decouple from the traffic platform.

Cloud platform design includes a traffic‑splitting system that maps user, version, and location info to experiment plans through concept, split, instance, and resource layers, enabling AB testing with minimal code changes.

Safety and disaster recovery: Three‑level client cache (memory, disk, pre‑packaged) and cloud‑side fallback data ensure page availability under network or service failures.

Interaction flow: Events triggered on the client are sent to the cloud via the protocol; the cloud returns data, and the client updates the UI, reducing client‑side logic and promoting data‑driven development.

Summary and outlook: The end‑to‑end containerized solution has been deployed across multiple Xianyu scenarios, providing dynamic page structure adjustment, reduced development effort, and faster rollout of new business pages.

frontendcloud-nativedynamic UICloud Platformcontainer protocol
Xianyu Technology
Written by

Xianyu Technology

Official account of the Xianyu technology team

0 followers
Reader feedback

How this landed with the community

login 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.