Layered architecture
Layered architecture is a software organization pattern that separates responsibilities into ordered layers with defined roles and constrained dependencies, typically from higher-level layers to lower-level ones.
Grokking Software Architecture
A structural division of software with a defined responsibility and relationships to other divisions.
- How it is used
- Organizes whole applications by responsibility to manage complexity and support maintenance.
- How deep it goes
- Defines four layers and dependency rules, addresses cross-cutting concerns and anti-patterns, and provides a sketching exercise.
- Examples
- Uses a blog-layer sketch, a repository swap, and a letter-delivery analogy for the OSI model.
- What you can do after
- Practice sketching application layers and assigning components by responsibility.
Read how Grokking Software Architecture explains layered architecture →
Microservices Patterns, Second Edition
An architectural style that organizes software elements into layers with defined responsibilities and constrained dependencies.
- How it is used
- Structures an application's domain view by assigning technical responsibilities to layers and constraining dependencies.
- How deep it goes
- Defines strict and relaxed dependency rules, maps three tiers, and identifies dependency and representation drawbacks.
- Examples
- Uses an FTGO monolith to show consumer, order, and notification code spread across web, domain, and persistence layers.
- What you can do after
- Evaluate whether technical layers fit an application by weighing dependency constraints against multiple interfaces, databases, and subdomain organization.
Read how Microservices Patterns, Second Edition explains layered architecture →
Functional Programming in C#, Second Edition
A software organization principle in which higher-level components depend on lower-level components, not vice versa.
- How it is used
- Structures applications so higher-level components compose lower-level functionality without upward dependencies.
- How deep it goes
- Defines dependency direction and contrasts adjacent-layer calls with composed workflows, but does not specify a complete implementation.
- Examples
- Contrasts a controller-to-repository-and-service hierarchy with a top-level workflow that composes lower-level functions.
- What you can do after
- Evaluate dependency direction and recognize how composition can isolate side effects and facilitate testing.
Read how Functional Programming in C#, Second Edition explains layered architecture →
Also covered in
- Clean Applications with Hexagonal ArchitectureIn early access (MEAP)
What to know first
- business logicBusiness logic is the domain-specific rules, computations, and decisions that determine how a software system processes operations and behaves.
Related concepts
- hexagonal architecturecontrasts with · Hexagonal architecture is a software architecture pattern that isolates an application's core logic behind ports and connects external systems through adapters.
- architectural stylekind of · An architectural pattern is a reusable high-level organization of software components, interactions, and constraints for addressing recurring system-design concerns.
- cross-cutting concerncontrasts with · A cross-cutting concern is a software responsibility or behavior that affects multiple components, features, or architectural layers rather than belonging to one alone.
- domain layerincludes · A domain layer is the architectural part of an application that contains its domain concepts, business rules, and behavior, distinct from infrastructure and delivery concerns.
- infrastructure layerincludes · An infrastructure layer is a software layer that provides technical capabilities and connects application functionality to external resources, services, or runtime facilities.
- OSI modelpart of · The OSI model is a seven-layer reference framework for organizing and describing the functions of communication between networked systems.
Questions about layered architecture
What is layered architecture?
Layered architecture is a software organization pattern that separates responsibilities into ordered layers with defined roles and constrained dependencies, typically from higher-level layers to lower-level ones.
Which Manning books explain layered architecture?
Grokking Software Architecture, Microservices Patterns, Second Edition and Functional Programming in C#, Second Edition.
What should I know before learning layered architecture?
Manning books that teach layered architecture usually introduce business logic first.
What is the difference between layered architecture and hexagonal architecture?
Layered architecture is a software organization pattern that separates responsibilities into ordered layers with defined roles and constrained dependencies, typically from higher-level layers to lower-level ones. Hexagonal architecture is a software architecture pattern that isolates an application's core logic behind ports and connects external systems through adapters.
What kinds of layered architecture are there?
Kinds of layered architecture include domain layer and infrastructure layer.
What is layered architecture a kind of?
Layered architecture is a kind of architectural style. An architectural pattern is a reusable high-level organization of software components, interactions, and constraints for addressing recurring system-design concerns.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


