Course contentsShow
← Software Engineering
Lesson 1223 of 1,93337. Software Architecture FundamentalsFree lesson

Architecture vs. Design

Distinguish between architectural decisions that affect the whole system and local design choices.

Architecture vs. Design

You'll learn: How to distinguish high-level architectural decisions that shape the entire system from lower-level design choices that affect individual components.

The Core Distinction

Architecture and design both deal with how software is structured, but they operate at different scales and have different impacts.

Architecture consists of decisions that are:

  • Hard to change later (high cost of reversal)
  • Affect multiple teams or components
  • Cross-cutting concerns that ripple throughout the system
  • Strategic choices about technology, structure, and key patterns

Design consists of decisions that are:

  • Local to a component, module, or class
  • Easier to change or refactor
  • Affect implementation details within boundaries
  • Tactical choices about algorithms, data structures, and class relationships

An Analogy

Think of building a house: Architecture is deciding where the load-bearing walls go, the plumbing layout, and the foundation type—expensive to change and affecting everything. Design is choosing cabinet hardware, paint colors, or flooring materials—still important, but changeable without rebuilding the house.

Examples

Architectural decisions:

  • Microservices vs. monolithic structure
  • SQL vs. NoSQL database choice
  • Synchronous HTTP vs. asynchronous messaging
  • Multi-region deployment strategy

Design decisions:

  • Which sorting algorithm to use in a function
  • Class inheritance vs. composition for a feature
  • Variable naming conventions
  • Internal module organization

Why It Matters

Understanding this boundary helps you know when to involve stakeholders broadly (architecture) versus when individual developers can proceed independently (design). It also guides where to invest in documentation, review processes, and decision records.

Key Takeaway: Architecture decisions affect the whole system and are costly to reverse; design decisions are local, tactical choices that can evolve within architectural boundaries.