Quality Attributes as Primary Drivers
You'll learn how non-functional requirements like performance and security fundamentally shape your architecture's core structure.
The Core Idea
While functional requirements tell you what your system must do ("allow users to log in"), quality attributes tell you how well it must do it ("respond in under 200ms, handle 10,000 concurrent users, keep data encrypted"). Here's the crucial insight: quality attributes drive architectural decisions far more powerfully than functional requirements.
Think of building a bridge. The functional requirement is simple: "get people across the river." But the quality attributes—must support 50-ton trucks, withstand earthquakes, last 100 years—fundamentally determine whether you build a rope bridge, steel suspension bridge, or concrete viaduct. Same destination, completely different structures.
Why Quality Attributes Dominate
Functional requirements can often be satisfied with many different architectures. You can implement user login with a monolith, microservices, serverless—all work functionally. But when you add quality attributes:
- Performance requirements (sub-100ms latency) → might force caching layers, CDNs, data denormalization
- Security requirements (zero-trust model) → demands authentication at every boundary, encryption everywhere
- Scalability requirements (handle 100x traffic spikes) → pushes toward stateless services, horizontal scaling
- Availability requirements (99.99% uptime) → requires redundancy, failover mechanisms, circuit breakers
These aren't features you add later—they're structural decisions you bake into the foundation. Change your mind about performance targets after building? You might rebuild the entire system.
Key Takeaway: Quality attributes like performance, security, scalability, and availability are the primary forces shaping your architecture's fundamental structure—they dictate patterns, technology choices, and system boundaries far more than functional requirements alone.