30 Software Architecture Principles for Effective System Design

The author, Srinath, a scientist, software architect, and co‑founder of the Apache Axis2 project, shares thirty architecture principles he has distilled from extensive experience in distributed systems, emphasizing that architects should act as guides and facilitators rather than sole designers.

Basic Principles : Emphasize simplicity (KISS), avoid unnecessary features (YAGNI), adopt an iterative "crawl‑walk‑run" approach, prioritize automated testing, consider ROI, understand users, design independent components, and avoid flashy, unused features.

Feature Selection : Embrace MVP, limit functionality, defer work until needed, and say no to users when a better solution exists, ensuring the product remains focused and valuable.

Server Design and Concurrency : Understand the full stack from hardware to language, minimize I/O calls, respect Amdahl's law, use concurrency only when necessary, keep lock hold times short, and avoid blocking in non‑blocking, event‑driven architectures.

Distributed Systems : Favor stateless designs, aim for at‑least‑once delivery with idempotent operations, be aware of CAP limitations, recognize that perfect consistency does not scale, and design for inevitable latency and failures.

User Experience : Know your audience, provide sensible defaults, avoid overwhelming users with configuration choices, ensure configuration values are understandable, and enforce validation with clear errors.

Difficult Issues : Resist the temptation to switch languages without strong justification, avoid overly complex drag‑and‑drop interfaces, and accept that perfect modularity is unrealistic in early project stages.

Conclusion : An architect should act like a gardener—pruning and guiding rather than dictating—using this widely accepted principle list as an anchor for discussions and as a learning path for junior architects.