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:
“For all Men would be Cowards if they durst:
And Honesty’s against all common sense—”
—John Wilmot, 2d Earl Of Rochester (1647–1680)
“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 have all my life been on my guard against the information conveyed by the sense of hearing—it being one of my earliest observations, the universal inclination of humankind is to be led by the ears, and I am sometimes apt to imagine that they are given to men as they are to pitchers, purposely that they may be carried about by them.”
—Mary Wortley, Lady Montagu (1689–1762)
“I need not say what match I would touch, what system endeavor to blow up; but as I love my life, I would side with the light, and let the dark earth roll from under me, calling my mother and my brother to follow.”
—Henry David Thoreau (1817–1862)
“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)
“Poetry is not only dream and vision; it is the skeleton architecture of our lives. It lays the foundations for a future of change, a bridge across our fears of what has never been before.”
—Audre Lorde (1934–1992)