topic / software-architecture

Software Architecture

Make boundaries and trade-offs visible before they become code.

Understand modularity, coupling, cohesion, dependency direction, design patterns, architecture styles, and the reasoning behind system boundaries and change.

1 article · 1 video · 1 trace · 1 request flow · 1 interview · 5 total

Articles

software architectureSep 25, 2026

Architecture Boundaries Are Decisions About Change

Use cohesion, coupling, and dependency direction to choose software boundaries that make likely changes easier to contain.

7 min readRead

Request Flows

request flow · 5 stagesA Stable Interface Contains a Changing ImplementationFollow a request through composition, a domain-facing interface, an adapter, and a concrete dependency.

Videos

In production

software architectureSep 25, 2026

Architecture Boundaries Without Boxes

A planned design review finds a change boundary by tracing dependencies, reasons to change, and failure behavior.

Details

Traces

trace 01 · applicationTrace a Strategy Call Across an InterfaceFollow a request from a stable caller through an injected policy interface to one selected implementation.

Interviews

medium · t2When Should You Add an Interface Boundary?An architecture prompt about likely changes, dependency direction, test seams, adapter costs, and unnecessary abstraction.

Explore adjacent

backend engineering system design software engineering distributed systems modularity and boundaries architecture styles design patterns

New lessons by email

Get new explanations about software architecture and related systems in your inbox.

One technical dispatch per week. No noise.