Insights on Software Architecture: Definitions, Evolution, Closed‑Loop Feedback, Microservices, and Organizational Culture

The author, with over ten years of experience in distributed system development at eBay China, Ctrip, and Vipshop, presents a platform‑centric view of software architecture, emphasizing that architecture is about identifying stakeholders and addressing their concerns.

Understanding Architecture – Architecture consists of elements and their relationships, is documented through multiple viewpoints, and each viewpoint resolves specific stakeholder concerns. The architect’s primary task is to discover all stakeholders (product managers, developers, testers, ops, etc.) and balance often conflicting concerns such as manageability versus performance.

Iteration and Evolution – Drawing on RUP principles (use‑case & risk driven, architecture‑centric, iterative & incremental), the author advocates building prototypes, stress‑testing them, and continuously iterating. Over‑engineering and neglecting MVP feedback loops are warned against; instead, small, frequent releases enable rapid learning and reduce risk.

Closed‑Loop Feedback Architecture – Inspired by DevOps, the article outlines three feedback layers: system‑level monitoring, application‑service monitoring, and customer‑experience monitoring, forming a continuous collect‑measure‑adjust cycle that drives ongoing improvement.

Microservices – Microservices embody single‑responsibility and separation‑of‑concerns, allowing independent development, testing, deployment, and evolution with low change cost. Adoption should consider system complexity and team size; premature microservice adoption can add unnecessary overhead.

Architecture and Organizational Culture – Conway’s Law is highlighted: system designs mirror communication structures. Aligning team organization with architecture (e.g., moving from monoliths to microservices) improves efficiency, while misalignment leads to friction and inefficiency.

Architect Mindset and Soft Skills – An open‑minded, “empty cup” attitude, continuous learning, and strong interpersonal skills are essential. Soft skills often outweigh technical prowess; architects must navigate politics, build relationships, and foster a culture of experimentation.

Controversial Topics – The author discusses the relationship between technology and business and whether architects should write code, concluding that answers depend on context and that hands‑on coding can keep architects grounded.

Conclusion – The Chinese internet ecosystem is growing, and aspiring architects should strive to emulate global leaders, continuously explore, and embrace the iterative, feedback‑driven nature of modern software architecture.