Backend Development 13 min read

Boundary Governance in Business Platform: Principles, Strategies, and Implementation

The article explains Yanxuan’s “boundary governance” approach—using horizontal layering and vertical domain decomposition to isolate complexity—by analyzing and redefining business, system, and organizational boundaries, planning twelve core business blocks, continuously reviewing them, and applying project‑based, consensus‑driven, and forward‑looking strategies to resolve boundary issues and strengthen the middle‑platform architecture.

NetEase Yanxuan Technology Product Team
NetEase Yanxuan Technology Product Team
NetEase Yanxuan Technology Product Team
Boundary Governance in Business Platform: Principles, Strategies, and Implementation

In 2019, the "Yanxuan" business platform began systematic construction of a middle‑platform, introducing the concept of “boundary governance”. This article, part of the series on the Yanxuan business middle‑platform, explains the basic ideas and implementation strategies of boundary governance.

Background: The 2019 “Yanxuan Business Middle‑Platform Whitepaper” marked the start of systematic middle‑platform building, and the term “boundary governance” has since become a frequent keyword.

Why boundary governance is needed: According to John Ousterhout’s “A Philosophy of Software Design”, the core goal of software design is to reduce complexity. Complexity arises from three sources – the problem domain itself, the technical architecture, and people/organizations. Uncontrolled changes in business, technology, organization, and cognition lead to chaotic systems.

Ousterhout proposes isolating complexity, which translates into two core engineering principles: horizontal architectural layering and vertical domain decomposition.

Horizontal layering isolates concerns through specialized divisions (e.g., front‑office, middle‑office, technical platform, infrastructure).

Vertical domain splitting refines responsibilities by analyzing and abstracting problem domains (e.g., transaction, user, marketing, inventory, etc.).

Yanxuan adopts boundary governance to isolate complexity via these two principles, preventing its spread.

Boundaries include horizontal layer boundaries, domain boundaries, system boundaries, and corresponding organizational boundaries. Governing these boundaries involves systematic analysis, review, and reconstruction of business, organization, and system structures, turning disorder into order.

Implementation is divided into two stages:

Stage 1 – “理” (Analysis) focuses on clarifying business boundaries, identifying boundary problems, and surfacing business capabilities. It follows three core steps: planning business blocks, delineating block and product boundaries, and maintaining freshness.

Planning business blocks: An architect team, using top‑down analysis, defines 12 core business blocks (transaction, user, marketing, etc.) based on e‑commerce expertise.

Boundary delineation: Product managers and developers apply domain‑analysis and boundary‑expression methods to produce architecture diagrams, identify boundary issues, and capture business capabilities.

Key principles for boundary delineation:

Emphasize target users and core problems.

Ensure high participation, especially from product managers.

Establish a “gate” review process with cross‑departmental architects.

Continuous freshness: Regularly review and adjust boundaries as business, technology, and organizational contexts evolve.

Identifying boundary problems: Common issues are duplicate construction and capability misalignment, which can cause resource waste and complex dependency chains.

Identifying business capabilities: Domain‑driven design helps create cohesive, low‑coupling boundaries and separate capability layers from operation platforms.

Stage 2 – “治” (Treatment) addresses the identified boundary problems by selecting appropriate governance solutions based on organization, technology, and business realities. Three core strategies are employed:

Project‑based execution: Use existing project mechanisms to solve boundary issues, prioritizing those with clear long‑term value.

Consensus and win‑win: Clarify that governance is not workload transfer but creates shared benefits.

Forward‑looking planning: Anticipate boundary issues early to avoid costly remediation later.

Conclusion: Since 2020, Yanxuan has treated boundary governance as a foundational practice, having refined 11 business blocks, identified dozens of boundary problems, and resolved over 60 % of them, thereby strengthening the middle‑platform architecture.

The ongoing goal is to embed boundary awareness into product development processes and daily work, improving collaboration efficiency and delivering greater value to users.

software architectureDomain-Driven Designdevelopment managementbusiness platformboundary governancesoftware complexity
NetEase Yanxuan Technology Product Team
Written by

NetEase Yanxuan Technology Product Team

The NetEase Yanxuan Technology Product Team shares practical tech insights for the e‑commerce ecosystem. This official channel periodically publishes technical articles, team events, recruitment information, and more.

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.