type: article

keywords:

• 3-Schichten-Modell
• 3-Tier Architektur
• Präsentation Business Daten
• DTO

canonicalURL: https://www.irc-coding.de/3-schichten-modell-3-tier-architektur

Software Architecture: 3-Layer Model / 3-Tier

This article is a glossary entry for the 3-Layer Model (3-Tier) – including exam questions, key points, and tags.

In a Nutshell

The 3-layer model logically separates software into presentation, business logic, and data access – for clear responsibilities, maintainability, and testability.

Compact Technical Description

The three layers:

1. Presentation (UI)
2. Business Logic (Services/Use Cases)
3. Persistence (Repository/ORM/DB)

Communication typically flows from top to bottom. Each layer only knows the one directly below it. This keeps systems loosely coupled.

Exam-Relevant Key Points

• Separation of presentation, logic, data access
• Clear responsibilities
• Better testability/maintainability
• Standard in Java/.NET/web projects (IHK-relevant)
• Components are exchangeable (UI switching)
• Layers are security barriers
• Modularization reduces follow-up costs
• Architecture must be documented

Core Components

1. Presentation layer
2. Logic layer
3. Data access layer
4. Interfaces between layers
5. Logging/error handling
6. Unit tests in business layer
7. DTOs
8. Security layer
9. Persistence (SQL/NoSQL)

Practical Example

UI (HTML/JS): Input
Business (Controller/Service): Validation/Processing
Persistence (ORM/MySQL): Storage

Advantages and Disadvantages

Advantages

• Structured, maintainable application
• Easy component exchange
• Good testability

Disadvantages

• More initial effort
• Overhead for very small projects

Typical Exam Questions (with Short Answer)

1. What does the 3-layer model describe? Presentation, logic, data access.
2. Which layer validates input? Business logic.
3. What belongs to the data access layer? DB access, SQL/ORM, repositories.

Free Response

For IHK projects, the model is ideal because it’s easy to draw and explain. Important: no SQL in the controller and no database access from the UI.

Learning Strategy

1. Draw the model for a system (shop/blog).
2. Implement a CRUD app strictly according to layers.
3. Explain layers in project documentation.
4. Implement separation technically through packages/namespaces.

Further Information

1. https://c4model.com/