what's the difference between application layer and business logic layer? I kind of understand that business layer provides business specific services and application layer couples business services and provides services to the end user (webservice, UI, etc) am i right?
views:
133answers:
5As I understand it the business layer is in charge of the business decisions AKA the logic involving the protocols of the client.
The application layer are the raw processes that have nothing to do with business decisions.
To summarize:
The application layer consists of those elements that are specific to this application. So that would contain the UI, back-end processing for the UI, and any bindings between the application and your business logic layer. In a perfect world, this layer would not contain any logic of the business domain.
The business logic layer (BLL) contains logic specific to the business domain. Also, if you are going to create a separate BLL, this layer should contain logic that could be used by other applications as well as this one. For example, a set of web services exposing a well-defined API. This de-couples the BLL from your application and allows you the flexibility to build other applications on top of it in the future.
Within the confines of Multitier architecture, the application layer and the business logic layer refer to the same thing. (I think this is what you're talking about.)
The term Application Layer is also used in protocol stacks, which can be confusing, but it's not really related. In this context it really encompasses all tiers of your application.
That sounds about correct.
The business layer implements the Domain Model in a boundary-technology-neutral way. In other words, it doesn't depend on any particular UI or service interface-related technology, such as web libraries or windowing APIs. You should be able to consume the business layer from any type of application - web, rich client, web service, etc.
The application layer bridges the gap between the business layer and the boundary techology.
I think of it as infrastructure. Depending on the application, it can contain the plumbing for configuration, reporting, the UI shell, etc.