The article explores structural thinking as the core mindset of software engineers, breaking it into three levels—conception, insight, and understanding—while emphasizing runtime and evolutionary structures for managing complexity, enabling collaboration, and sustaining long-term system health.
The article explains architectural thinking as a systematic approach to decompose problems, highlighting five core principles—abstraction, global perspective, layered design, evolutionary mindset, and standardization—that help engineers manage complexity, improve design quality, and adapt software systems over time.
This article presents a comprehensive case study of how Qunar's hotel supply‑chain team applied Domain‑Driven Design to restructure a decade‑old, highly coupled hotel information system, detailing the problem analysis, DDD rationale, evolutionary transformation process, architectural principles, implementation results, and lessons learned.
The article analyzes current and emerging software architecture trends such as evolutionary architecture, microservices adoption, event sourcing, serverless, and the evolving role of architects, highlighting which concepts are moving toward mainstream adoption and which remain niche.
The article explains how abstraction, layered design, divide‑and‑conquer, and evolutionary thinking form the four essential mental tools for architects to manage complexity, illustrating each concept with real‑world examples, diagrams, and practical advice for cultivating these skills.
This article examines evolutionary architecture for microservices, outlines popular patterns such as CI/CD and the Strangler approach, explains layered and bounded‑context designs, and provides a detailed case study showing how a legacy monolithic system can be incrementally refactored into a flexible, cloud‑native microservice ecosystem.
