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

Architecture as Decisions

Explore how architecture consists of significant decisions that are costly to change later in development.

Architecture as Decisions

What you'll learn: How software architecture fundamentally consists of making significant design choices that become expensive to reverse later.

The Core Idea

While we previously looked at architecture as structure (lesson 1220), there's another powerful lens: architecture is the sum of important decisions you make about how your system works. Not every choice is architectural—deciding on a variable name isn't—but choosing between a microservices or monolithic structure? That's architectural.

Think of architecture like choosing where to build roads in a new city. Once concrete is poured and buildings rise around those roads, moving them becomes extraordinarily expensive. You can repaint the lines easily, but rerouting a highway? That requires demolishing buildings, relocating utilities, and disrupting thousands of lives.

What Makes a Decision Architectural?

A decision qualifies as architectural when:

  • It's costly to change later — refactoring would require touching many parts of the system
  • It affects multiple components — the choice ripples through your codebase
  • It constrains future options — you're committing to certain paths and closing others
  • It's fundamental to how the system operates — like choosing synchronous vs. asynchronous communication patterns

Examples: selecting a database technology, defining service boundaries, choosing a messaging protocol, establishing authentication mechanisms, or deciding how services discover each other.

Why This Matters

Understanding architecture as decisions helps you:

  • Recognize when you're making a choice that needs careful consideration and documentation
  • Avoid accidentally "architecting by default" without conscious thought
  • Know when to involve senior engineers or architects in design discussions
  • Capture the why behind choices, not just the what

Key Takeaway: Architecture isn't just the structure you end up with—it's the critical, hard-to-reverse decisions you make along the way. Treat these choices with appropriate gravity and documentation.