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:
“There is all the poetry in the world in a name. It is a poem which the mass of men hear and read. What is poetry in the common sense, but a hearing of such jingling names? I want nothing better than a good word. The name of a thing may easily be more than the thing itself to me.”
—Henry David Thoreau (1817–1862)
“I think it’s the real world. The people we’re writing about in professional sports, they’re suffering and living and dying and loving and trying to make their way through life just as the brick layers and politicians are.”
—Walter Wellesley (Red)
“English literature is a kind of training in social ethics.... English trains you to handle a body of information in a way that is conducive to action.”
—Marilyn Butler (b. 1937)
“New York is more now than the sum of its people and buildings. It makes sense only as a mechanical intelligence, a transporter system for the daily absorbing and nightly redeploying of the human multitudes whose services it requires.”
—Peter Conrad (b. 1948)
“It was at that moment, just after Krug had fallen through the bottom of a confused dream and sat up on the straw with a gasp—and just before his reality, his remembered hideous misfortune could pounce upon him—it was then that I felt a pang of pity for Adam and slid towards him along an inclined beam of pale light—causing instantaneous madness, but at least saving him from the senseless agony of his logical fate.”
—Vladimir Nabokov (1899–1977)
“They can do without architecture who have no olives nor wines in the cellar.”
—Henry David Thoreau (1817–1862)