What Makes a Great System Architect? Lessons from Alibaba’s Business Platform

My Understanding of Technical Architecture

Top‑level design is akin to a national five‑year plan: a clear macro architecture that defines goals and outcomes precisely. Large‑scale events like Double 11 need such design to ensure low cost, high efficiency, high stability, and integration of new technologies.

Physical Architecture

Alibaba’s unitized architecture differs fundamentally from other companies. By deploying isolated units across distant data centers, production traffic can run continuously off‑site, emphasizing isolation, distance, and continuity.

Application Architecture

The “StarRing” platform abstracts code co‑development into horizontal and vertical business packages, achieving isolation between business services and the platform. This reduces tangled if‑else logic across dozens of BUs and simplifies development, testing, and deployment.

Architect Role

Architects must maintain a dispersed yet cohesive mindset, abstracting technical problems to solve entire classes of issues. They need foresight, extensive practice, and the ability to learn from past generations while applying new methods to emerging problems.

What Abilities an Architect Needs

Discover problems : Spot both existing and latent issues, distinguishing between symptomatic and root‑cause fixes.

Define and analyze problems : Abstract and articulate problem elements, set short‑ and long‑term solutions, and drive technical progress.

Solve problems : Design implementation paths, coordinate teams and stakeholders, and ensure global rather than local solutions.

Communication : Clearly convey issues and solutions to upstream and downstream partners, fostering consensus.

Fire‑fighting : Not only resolve immediate incidents but also anticipate and prevent future failures.

Challenges for Architects

A global perspective is essential; understanding a feature like “membership” requires seeing its connections to shopping, transactions, and user flows. Technical breadth—covering iOS, Android, PC, CDN, networking, service discovery, routing, HSF, databases, and messaging—is crucial, as is deep knowledge of underlying layers such as networks and storage.

Continuous learning is vital. The author dedicates 2‑3 hours daily to systematic study, from low‑level protocols to cutting‑edge research papers, building a knowledge base that enables rapid problem diagnosis and innovative solutions.

Business understanding ties everything together: architecture must serve business goals, and architects must integrate technical insight with practical business needs to achieve cost reduction, efficiency gains, and sustainable results.