Key Architectural Practices and Insights for Scalable, High‑Availability Systems

Architecture and the role of architects are constantly discussed, raising questions such as what architecture entails, how to design front‑back separation, high‑availability, scalability, and the qualities required of an architect.

Li Zhihui advises startup engineers to master scalable web development, describing the evolution from single‑machine deployment to independent module deployment and finally cluster deployment, highlighting core technologies like load balancers, distributed caches, master‑slave replication, and distributed databases, as well as team organization strategies for agile, small‑team structures.

Li Yunhua introduces a business‑centric three‑dimensional high‑availability design, shifting focus from system‑level to business‑level availability with measurable targets (e.g., 3‑minute problem localization, 5‑minute recovery), and proposes solutions such as client retries, HTTP‑DNS, function isolation, degradation, and multi‑active sites, supported by automated, visual monitoring.

Huang Yong’s "From MVC to Front‑Back Separation" examines MVC’s strengths and weaknesses, then presents REST‑based front‑back separation, illustrating the construction of a REST framework through a practical scenario and detailing core technologies and implementation steps.

Sun Xuan uses 58.com’s "58 Bangbang" as a case study, outlining four architectural stages—from traditional instant messaging to merchant management, mobile marketing tools, and push notification systems—supporting over one billion daily requests and more than one million concurrent users.

Liu Hongfeng discusses industrial‑grade IoT architecture, differentiating "Internet+" from IoT, and describing design across device, cloud, and monitoring layers, including middleware considerations, with examples such as remote health monitoring, agricultural greenhouse control, offshore fishery monitoring, and village wastewater treatment.

Ye Yurui presents an overview of Software‑Defined Storage (SDS), defining SDS, its classifications, and its relationship to VMware’s Software‑Defined Data Center (SDDC), which encompasses compute, storage, network, management, and security components, and explains the abstraction, pooling, and automation stages.

Zhuang Biaowei reflects on the inner cultivation of architects, emphasizing the need for both hard technical abilities and soft interpersonal skills, deep user understanding, leadership, risk avoidance, continuous learning, and balanced self‑improvement.

Deng Fanping shares Android architecture practices from his experiences at Tieto, Sony, and Minsheng Bank, illustrating that architecture is ubiquitous, requiring clear blueprints, strong execution, and keen risk awareness, encapsulated in the notion that "architecture exists everywhere in life."

Copyright notice: content sourced from the web, rights belong to original authors; attribution is provided where possible, and any infringement will be addressed promptly.