What Makes a Great Software Architecture? Insights for Aspiring Architects

On a relaxed weekend, the author shares an extra chapter from an internal PPT about what a software architect is and what software architecture means.

Definition of Architecture

Software architecture is a set of structures describing the components, their externally visible properties, and relationships. It is not executable code but a representation that helps engineers analyze design effectiveness, consider alternatives early, and reduce construction risk.

Software Architecture Lifecycle

Just as software development follows a lifecycle, architecture itself has a lifecycle, illustrated by the following diagram:

The architecture lifecycle mirrors the stages of software development.

Why Architecture Matters

Ensures system quality.

Aligns stakeholders on common goals.

Supports planning and design processes.

Guides system development.

Manages complexity effectively.

Lays the foundation for reuse.

Reduces maintenance costs.

Facilitates conflict analysis.

What Makes a Good Architecture

Good architecture resembles LEGO blocks: high cohesion, low coupling, and standardized interfaces that allow flexible re‑assembly.

Bad architecture is compared to chaotic, hard‑to‑maintain structures, illustrated by images of disordered text and mismatched designs.

Successful Software and Architecture

Successful software reflects a well‑designed architecture. Examples include modular warships versus poorly integrated designs, highlighting the benefits of replaceable modules.

The Beauty of Architecture

Architecture is likened to martial arts—agile, unconventional, and capable of overcoming traditional constraints. It is also compared to art pieces, emphasizing that a simple design can be a masterpiece.

Key Considerations

A good architecture should not be limited by frameworks, languages, or specific technologies; it is an artistic vision.

Java‑Related Technical Knowledge

For Java architects, essential skills include understanding common domains (e‑commerce, finance, etc.), middleware, databases, and development frameworks.

Architects' Responsibilities

Architects focus on non‑functional requirements such as performance (<2 s response time), scalability (1000 concurrent users), extensibility, security protocols, and integration with LDAP.

Many mistakenly view architects only as troubleshooters, but their role is to anticipate and design solutions before problems arise.

Types of Architects

Business Architect (BA)

System Architect (SA)

In practice, system and application architects are often grouped together.

What Architects Do Daily

Architects engage in activities like requirement analysis, design reviews, technology evaluation, and guiding development teams, as shown in the accompanying diagram.

Limitations and Soft Skills

Architects are powerful but not superhuman; they need soft skills such as communication, leadership, and continuous learning.

Self‑Improvement and Mindset

Continuous learning, mastering fundamentals, and maintaining a positive mindset are essential. The author emphasizes adapting to change, leveraging imperfections as strengths, and staying motivated.