Mastering the ‘9 Swords’ Architecture: A Senior Architect’s 20‑Year Blueprint for Business, Product, and Application Design

Overview

The article introduces the "9 Swords" architecture framework distilled from a senior architect’s 20‑year experience, aiming to help engineers transform vague requirements into concrete, interview‑ready architecture designs.

Core 1 – Business Architecture (Strategic Blueprint)

Business architecture translates high‑level goals (e.g., building an e‑commerce platform) into actionable plans through four steps: problem‑domain analysis, product‑direction definition, process mapping, and functional matrix creation.

Problem Domain : Identify pain points, market gaps, and constraints. Example for an e‑commerce platform includes supplier‑management inefficiency, low user repurchase rate, and high logistics cost.

Product Direction : Define value proposition, user segmentation, and key metrics (e.g., GMV, retention).

Business Process : Visualize end‑to‑end flow with swim‑lane diagrams; sample flow:

用户下单 → 风控审核 → 仓库分拣 → 物流调度 → 用户签收

.

Function Matrix : Prioritize features using MoSCoW, map them to problem domains, and illustrate dependencies in a table (e.g., intelligent recommendation engine – P0 – depends on user‑data platform).

Core 2 – Product Architecture (User‑Centric Feature Skeleton)

Product architecture organizes functional modules into layers: presentation (UI/UX), service (business logic), core (core capabilities), and data (storage). It defines clear module boundaries to avoid overlap.

Layered Model : Example table shows UI/UX (product list, cart), Service (search, recommendation, risk), Core (order, inventory, payment), Data (user DB, product DB, logs).

Boundary Definition : Use use‑case diagrams to split features (e.g., search vs filter) and avoid “god modules”.

Core 3 – Application Architecture (Technical Implementation)

Application architecture bridges business needs to technical solutions, balancing performance, scalability, complexity, and cost. Two primary styles are discussed:

Monolithic Architecture : Simple deployment, suitable for early‑stage or small‑scale projects. Advantages: easy development and deployment. Disadvantages: hard to scale, single point of failure.

Distributed Architecture : Decomposes system into independent services (microservices, service mesh). Advantages: independent scaling, fault isolation. Disadvantages: higher operational complexity, need for service discovery and consistency mechanisms.

Evolution path: start with a monolith for rapid validation, then extract high‑frequency services (e.g., recommendation) into microservices, and finally adopt service‑mesh patterns for mature systems.

用户下单 → 风控审核 → 仓库分拣 → 物流调度 → 用户签收

Design Principles

Upper layers depend on lower layers (UI → Service → Core).

Decouple modules within the same layer to avoid tight coupling (e.g., payment should not directly depend on recommendation).

Boundary Visualization

Use color‑coded diagrams to distinguish owned modules, third‑party services, and shared infrastructure, making responsibilities clear at a glance.

Practical Walkthroughs

Step‑by‑step case studies illustrate how to apply the framework to a risk‑control system, covering problem‑domain extraction, product direction, process mapping, function matrix creation, and eventual application‑level design (both monolithic and distributed).

By following the nine‑step "9 Swords" methodology, engineers can systematically produce clear, defensible architecture proposals that satisfy interviewers and guide real‑world system design.