Layered Architecture

The Layered Architecture is a well-established architectural pattern that divides systems into different layers, each with a specific responsibility. This pattern promotes modularity and allows for a clear separation of concerns, improving the maintainability and extensibility of software systems.

Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.

Content type

Concept

Theoretical construct: explains a term, principle, or mental model.

Classification level

Structure

What organizes, connects, or makes decisions possible.

Available perspectives

Open this building block directly in an already curated view.

360°

In brief

Layered architecture in brief

Layered architecture structures software into stacked layers with distinct responsibilities and directed dependencies, such as presentation, application, domain, and infrastructure.

Where does it come from?

Layering applies separation of concerns from software and systems architecture to a concrete structure. Multitier and n-tier architectures made the separation of user interface, business logic, and data access a common organizational form.

The mental model

Think of a building with floors: interaction sits above application logic, domain rules form the core, and technical adapters sit below. Each floor uses defined services of the one beneath it so changes stay contained.

Key building blocks

Layer

It groups code around a shared responsibility and hides internal details from other layers.

Dependency direction

It defines which layer may know and call another layer.

When is it useful?

The pattern helps teams organize responsibilities and limit change impact. It becomes harmful when layers are mere pass-throughs or dependencies cross their intended boundaries.

Layered Architecture - Ein Überblick Best Practices für Layered Architecture Layered Architecture in der Softwareentwicklung