Architecture boundaries & dependencies

Compare layers and inward-facing boundaries to decide where business rules live and which dependencies may change.

Search within: Architecture boundaries & dependencies

3 field notes

Point source dependencies inward to protect application policy.

Separate application rules from input and storage technologies through ports and replaceable adapters.

Separate stable responsibilities along a simple dependency path.

Comparison within this category
Concept	Features	Advantages	Limitations	Suitable situations	Combination conditions
Clean architecture	Source dependencies point inward	Policy stays independent of framework data	Boundary mapping adds maintenance	Policy must outlive UI and database choices	Can use hexagonal ports at the edges
Hexagonal architecture	Application ports and external adapters	Test saving with an in-memory adapter	Ports and adapters add indirection	Multiple entry points or storage implementations	Can organize internal policy with clean architecture
Layered architecture	Responsibility layers with downward dependencies	Validation has a clear home	Pass-through layers add ceremony	Stable presentation, application and storage roles	Can add ports and dependency inversion