n-Tier Architecture
Definition
A multilayer architecture distributes tasks across separately operable system parts.
A system architecture that distributes presentation, business logic, or data storage across multiple separately operable tiers; logical layers can be tailored independently of this.
Simply explained
The visible interface, processing, and data storage can run on different stations.
Why it matters in practice
Helps develop and operate digital systems robustly, securely, and maintainably.
Example from business
Web interface, application service, and database are operated separately.
Limits and pitfalls
- Equating logical layers with physical tiers, introducing unnecessarily many network boundaries, or allowing dependencies to regress disorderly.
Origin & history
Multilayer architectures became widespread with client-server and enterprise systems.
Use in mid-sized companies
- Possible application: Web interface, application service, and database are operated separately.
Frequently asked questions
What does multilayer architecture (n-tier) mean?
A system architecture that distributes presentation, business logic, or data storage across multiple separately operable tiers; logical layers can be tailored independently of this.
Which mistakes should be avoided?
Equating logical layers with physical tiers, introducing unnecessarily many network boundaries, or allowing dependencies to regress disorderly.
Sources
Source checked on 10.10.2026. Editorial application examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: