# Layered Architecture

> An app split into stacked layers. Each one calls only the one below.

**Field:** Software Development  
**Category:** Architecture  
**Also known as:** N-Tier Architecture, Three-Tier Architecture, Layers

## Think of it like

Think of it like a cake with layers. Each layer sits only on the one below it.

## Definition

Layered architecture splits an app into stacked layers, each with one kind of job. A common set is three: the screens, the business rules and the data access. Each layer only calls the layer just below it. So the screens never talk to the database directly. It is easy to understand, which is why so many apps start this way.

## Example

In Jack's app, a button calls the order rules layer. That layer calls the data layer, which talks to the database. The button never touches the database.

## Why it matters

Clear layers tell everyone where new code goes, which keeps a growing app in order.

## Common mistake

Letting the rules of the business lean on how the database works. Then a new database means new rules too.

## Three principles

- **Stacked layers.** One kind of job each.
- **Call one down.** Never skip a layer.
- **Easy to grasp.** A common first shape.

## Related terms

- [Abstraction Layer](https://learn.benibix.com/term/development/abstraction-layer)
- [Separation of Concerns](https://learn.benibix.com/term/development/separation-of-concerns)
- [Model-View-Controller (MVC)](https://learn.benibix.com/term/development/mvc)
- [Clean Architecture](https://learn.benibix.com/term/development/clean-architecture)

---

Source: https://learn.benibix.com/term/development/layered-architecture
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
