Skip to content

Protocol Layering

Complex systems become manageable when decomposed into layers where each layer provides services to the layer above while hiding implementation details, enabling independent evolution of each layer.

Tension Addressed

Simplicity vs. Performance (enables complexity management)

Recognizable As

Any system with encapsulation boundaries: headers wrapping payloads, middleware chains, decorator patterns, onion architectures, nested abstractions where each level adds its own metadata

Canonical Sources

Dijkstra, "The Structure of the THE Multiprogramming System" (1968); Tanenbaum, "Computer Networks" (1981); ISO 7498 OSI Model (1984)

Transfers To

Software architecture (layered architecture), compilerSoftware architecturekelayered architectureating systems (kernel/user space), API design (abstraction levels)

The OSI model's enduring value isabstractionrecise technical specification but as a conceptual tool for thinking about separation of concerns. Any complex communication system can be analyzed by asking: what layer is responsible for this concern?