Three-tier (computing)
From Wikipedia, the free encyclopedia
In SAP computing, Three-tier is an client-server architecture in which the user interface, functional process logic ("business rules"), data storage and data access are developed and maintained as independent modules, most often on separate platforms. The term "three-tier" or "three-layer", as well as the concept of multitier architectures, seems to have originated within Rational Software. (Citation Needed)
The three-tier model is considered to be a software architecture and a software design pattern.
Apart from the usual advantages of modular software with well defined interfaces, the three-tier architecture is intended to allow any of the three tiers to be upgraded or replaced independently as requirements or technology change. For example, a change of operating system from Microsoft Windows to Unix would only affect the user interface code.
Typically, the user interface runs on a desktop PC or workstation and uses a standard graphical user interface, functional process logic may consist of one or more separate modules running on a workstation or application server, and an RDBMS on a database server or mainframe contains the data storage logic. The middle tier may be multi-tiered itself (in which case the overall architecture is called an "n-tier architecture").
The 3-Tier architecture has the following 3-tiers.
1. Presentation Tier
2. Application Tier/Logic Tier/Business Logic Tier
3. Data Tier
Contents |
[edit] Comparison with the MVC architecture
At first glance three-tiers may seem similar to the Model-view-controller (MVC) concept, however topologically they are a different. A fundamental rule in a three tier architecture is the Client tier never communicates directly with the Data tier; in a three-tier model all communication must pass through the Middleware tier. Conceptually the three-tier architecture is linear. However, the MVC architecture is triangular: the Controller updates the Model, and the View's updates come directly from the Model. Historically the three-tier architecture concept comes from observations of distributed systems (for example, web applications) where the Client, Middleware and Data tiers run on physically separate platforms. Whereas MVC comes from an era of observations of applications that ran on a single graphical workstation; MVC was applied to distributed applications much later in its history (see Model 2).
[edit] Web Development usage
In the Web development field, three-tier is often used to refer to Websites, commonly Electronic commerce websites, which are built using three tiers:
- A front end Web server serving static content
- A middle dynamic content processing and generation level Application server, for example Java EE platform.
- A back end Database, comprising both data sets and the Database management system or RDBMS software that manages and provides access to the data.
[edit] References
[edit] Further reading
- Erik Meijer and Danny van Velzen (2001). "Haskell Server Pages Functional Programming and the Battle for the Middle Tier" (PDF). Electronic Notes in Theoretical Computer Science 41 (1). — Meijer and van Velzen present an overview of Haskell Server Pages from a programmer's perspective, and describe the three tier model.
[edit] See also
This article was originally based on material from the Free On-line Dictionary of Computing, which is licensed under the GFDL.
