Layered Architecture
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
In a layered architecture the system is sliced by abstraction or responsibility into layers, where each layer depends only on the layer immediately below it and offers services to the one above, through stable interfaces. The mechanism is separation of concerns: volatile parts are separated from stable ones, higher-level policy is decoupled from lower-level implementation, and a single layer can be replaced without disturbing the others. Familiar instances include the OSI seven-layer model, corporate hierarchy, and Maslow's hierarchy of needs.
SCAFFOLDING EFFECT
Reduce cognitive load
- Slice by responsibility: cut the system into layers with one job each. - Fix the interfaces: allow calls only between adjacent layers so dependencies stay one-way. - Swap freely: replace any layer that still honors the interface contract.
Anchor fast decisions
Dependencies are forced to flow in one direction through stable interfaces, so a change inside one layer cannot ripple arbitrarily through the system. Because each layer hides its internal complexity from the one above, the total cognitive load is roughly the sum of the layers rather than their product.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Multitier_architectureverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS