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:
“A man of rare common sense and directness of speech, as of action; a transcendentalist above all, a man of ideas and principles,Mthat was what distinguished him.”
—Henry David Thoreau (1817–1862)
“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)
“I am the very pattern of a modern Major-Gineral,
I’ve information vegetable, animal, and mineral;
I know the kings of England, and I quote the fights historical,
From Marathon to Waterloo, in order categorical;”
—Sir William Schwenck Gilbert (1836–1911)
“... in America ... children are instructed in the virtues of the system they live under, as though history had achieved a happy ending in American civics.”
—Mary McCarthy (1912–1989)
“The logical English train a scholar as they train an engineer. Oxford is Greek factory, as Wilton mills weave carpet, and Sheffield grinds steel. They know the use of a tutor, as they know the use of a horse; and they draw the greatest amount of benefit from both. The reading men are kept by hard walking, hard riding, and measured eating and drinking, at the top of their condition, and two days before the examination, do not work but lounge, ride, or run, to be fresh on the college doomsday.”
—Ralph Waldo Emerson (1803–1882)
“I don’t think of form as a kind of architecture. The architecture is the result of the forming. It is the kinesthetic and visual sense of position and wholeness that puts the thing into the realm of art.”
—Roy Lichtenstein (b. 1923)