The following four layers are the most common layers in a logical multilayered architecture for an information system with an object-oriented design:
- Presentation Layer (a.k.a. UI Layer, View Layer, Presentation Tier.)
- Application Layer (a.k.a. Service Layer or GRASP Controller Layer )
- Business Layer (a.k.a Business logic layer (BLL))
- Infrastructure Layer (Data access layer, Persistence layer, Logging, Networking, and other Services which are required to support a particular Business Layer.)
Some common purposes of the above four layers are for example described in the book about domain-driven design at page 68-74, which is a book that otherwise is focused on describing the Domain layer
Sometimes there is no explicit distinction between the Business Layer and the Application Layer, e.g. the Application Layer is considered as being a part of the Business Layer. On the other hand, it is also possible to even further divide the Application/Business Layers into more layers. For example, if the Model View Presenter pattern is used, then you can consider the Presenter Layer as being a layer between the User Interface Layer and the Application Layer.
The Business Layer can also use a Business Infrastructure Layer (aka low-level business 'services' layer) logically positioned between Business Layer(s) and Infrastructure Layer(s). That layer (BI) is very general and can be used in several application tiers, e.g. a CurrencyConverter.
The Infrastructure Layer may be partitioned into different levels (high-level or low-level technical services). Though, it is not unusual that developers only consider the persistence (data access) and therefore only talk about the Persistence Layer or the Data Access Layer (instead of an Infrastructure Layer or Technical services Layer). In other words, the other kind of technical services are not always being explicitly thought of as being part of any particular layer.
Regarding that all types are not always considered as belonging to one particular layer, according to the "POSA book" (Pattern-Oriented Software Architecture A System of Patterns, page 39) a relaxed layered system (as opposed to a strict layered system) can use so called "shared data definition modules" which are types not belonging in a particular layer.
Famous quotes containing the words common, layers, information, system, logical and/or architecture:
“Poetry, at all times, exercises two distinct functions: it may reveal, it may unveil to every eye, the ideal aspects of common things ... or it may actually add to the number of motives poetic and uncommon in themselves, by the imaginative creation of things that are ideal from their very birth.”
—Walter Pater (1839–1894)
“The force of a death should be enormous but how can you know what kind of man you’ve killed or who was the braver and stronger if you have to peer through layers of glass that deliver the image but obscure the meaning of the act? War has a conscience or it’s ordinary murder.”
—Don Delillo (b. 1926)
“Rejecting all organs of information ... but my senses, I rid myself of the Pyrrhonisms with which an indulgence in speculations hyperphysical and antiphysical so uselessly occupy and disquiet the mind.”
—Thomas Jefferson (1743–1826)
“For the universe has three children, born at one time, which reappear, under different names, in every system of thought, whether they be called cause, operation, and effect; or, more poetically, Jove, Pluto, Neptune; or, theologically, the Father, the Spirit, and the Son; but which we will call here, the Knower, the Doer, and the Sayer. These stand respectively for the love of truth, for the love of good, and for the love of beauty.”
—Ralph Waldo Emerson (1803–1882)
“There is no logical reason why the camel of great art should pass through the needle of mob intelligence.”
—Rebecca West (1892–1983)
“Defaced ruins of architecture and statuary, like the wrinkles of decrepitude of a once beautiful woman, only make one regret that one did not see them when they were enchanting.”
—Horace Walpole (1717–1797)