Understanding Software Architecture: Definitions, Goals, Best Practices, and the Path to Becoming an Architect

Because fragmented time allowed the author to reflect on architecture, they compiled observations and questions from the past two years into a record for future reference.

1. Definition of Architecture

Software architecture is an abstract description of a system’s overall structure and components, guiding the design of large‑scale software (quoted from Baidu Baike).

2. What Architecture Does

Architecture is not just about performance, TPS, or high availability; it provides a shared set of rules for larger teams, reduces friction, and aligns development toward common goals.

Typical problems that arise in bigger teams include integration with existing systems, upstream module quality, differing design opinions, code style inconsistency, duplicated non‑business code, and boundary disagreements.

Good architecture balances trade‑offs, choosing solutions with the optimal cost‑benefit ratio.

3. Best Practices for Architecture

Abstraction is key; using diagrams such as use‑case diagrams and robustness diagrams helps visualize and evaluate designs.

These diagrams describe interactions with external entities and identify information and control flows.

When planning architectural changes, consider team ownership, domain‑oriented boundaries, collaboration impact, and core vs. non‑core separation.

Selection of middleware or frameworks should be based on maturity, community activity, hard technical requirements (performance, scalability), soft factors (complexity, maintainability), and hands‑on validation.

4. What Makes a Good Architecture

A good architecture aligns tightly with business needs, avoids over‑engineering, and evaluates solutions by their return on investment, considering both benefits (reliability, scalability, maintainability) and costs (people, time, risk).

5. How to Become an Architect

An architect must be a motivated “good coder” who combines deep technical skill with business understanding, communication ability, and personal influence, continuously expanding knowledge from depth to breadth.

Practical experience is essential; purely theoretical knowledge is insufficient.

6. Conclusion

Architecture concepts apply to both monolithic and distributed systems; the core ideas remain the same, though tools differ. The journey of mastering architecture is long and continuous.