Clean architecture
Point source dependencies toward policy.
Open field noteArchitecture boundaries & dependencies
Explore Architecture boundaries & dependencies.
3 field notes
| 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 |