Multitier architecture
computing system architecture that may typically have three tiers, composed of a presentation tier, a domain logic tier, and a data storage tier

In software engineering, multitier architecture (often referred to as n-tier architecture or layered architecture) is a client–server architecture in which various levels of software architecture are physically separated. The most common use of multitier architecture is the three-tier architecture, which separates presentation, application processing and data management functions, such as in the case of Cisco's hierarchical internetworking model. Other tiers of separation may include the service layer, business layer, data access layer, and persistence layer.
N-tier application architecture provides a model by which developers can modify or add to a specific tier in the software development process instead of reworking the entire application. It is commonly used for small and simple applications because of its simplicity and low cost. In web development, three-tier architecture is often used to describe websites that comprise a front-end web server serving static content and some cached dynamic content, a middle dynamic content processing and generation application server, and a back-end database or data store.
In a strict layered system, each layer depends on the layer below it and can exist without the layers above it. In a relaxed layered system, a layer can also depend on all of the layers below it, creating additional couplings between layers. Some multitier architectures use a hybrid approach so that some layers are strict while other layers are relaxed. N-tier architecture may also be implemented with the model–view–presenter pattern.
The public source identifies “Multitier architecture” as computing system architecture that may typically have three tiers, composed of a presentation tier, a domain logic tier, and a data storage tier. This brief keeps that definition visible, then builds a research path around Multitier, architecture and computing.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Multitier architecture”, the useful work is to connect “computing system architecture that may typically have three tiers, composed of a presentation tier, a domain logic tier, and a data storage tier” to the records capable of establishing context and consequence.
Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Jul 22, 2026. The linked authority identifier is Q1052721. None of the 0 selected statements returned an explicit reference.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Multitier architecture”, its source revision and the description used here.
- Expand the search: follow Multitier architecture primary sources, Multitier architecture archive and Multitier research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Multitier architecture”?
- What physical evidence or contemporary plan supports the description?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Multitier architecture” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.