Architecture & design

Architecture is about dependency direction and blast radius: who may call whom, how data flows, and how failures are isolated. This chapter avoids buzzwords (“microservices vs monolith”) in favor of layering and boundary rules you can apply tomorrow.

Division of labor with foundations · concurrency: fundamentals keep a module correct; architecture keeps many modules evolvable together.

Scope

Topic	Focus
Layering	Presentation / application / domain / infrastructure roles
Boundaries	APIs, anti-corruption layers between modules and services

Articles

Topic	Page
Layering & dependencies	layering
Boundaries & contracts	boundaries

See also

• Hub: Software development
• Delivery & contract tests: CI/CD
• Stack constraints: frontend, mobile