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:
“At the next town
the local princess was having a contest.
A common way for princesses to marry.
Fifty men had perished,
gargling the sea like soup.”
—Anne Sexton (1928–1974)
“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)
“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)
“If mothers are to be successful in achieving their child-rearing goals, they must have the inner freedom to find their own value system and within that system to find what is acceptable to them and what is not. This means leaving behind the anxiety, but also the security, of simplistic good-bad formulations and deciding for themselves what they want to teach their children.”
—Elaine Heffner (20th century)
“The novel is not “a crazy quilt of bits”; it is a logical sequence of psychological events: the movements of stars may seem crazy to the simpleton, but wise men know the comets come back.”
—Vladimir Nabokov (1899–1977)
“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)