layered architecture

Organising a system into ranked layers where each layer may only use layers below it.

In more detail

In an application the layers might be request handling, business logic and data access; in a design system they might be tokens, primitives, components and page templates. Dependencies flow in one direction only, from higher layers down to lower ones. That rule prevents circular dependencies and lets you change a lower layer knowing exactly what sits on top of it.

Example

The lesson registry gives token.color layer 0 and button.atom layer 1, and rejects any node whose dependency sits on the same or a higher layer.

Related terms

Taught in

References