Service layer pattern
(New page: The definition for the Service Layer Pattern is “defines an application’s boundary with a layer of services that establishes a set of available operations and coordinates the applicati...) |
|||
| Line 4: | Line 4: | ||
There are two ways of implementing the Service Layer Pattern. One is the domain façade approach which builds a façade to invoke the business logic provided by the domain logic classes. Another approach is named the operation script approach, which builds a layer of classes for the application logic with the encapsulated business logic from those business logic classes. | There are two ways of implementing the Service Layer Pattern. One is the domain façade approach which builds a façade to invoke the business logic provided by the domain logic classes. Another approach is named the operation script approach, which builds a layer of classes for the application logic with the encapsulated business logic from those business logic classes. | ||
| − | |||
==== When to Use It ==== | ==== When to Use It ==== | ||
The Service Layer patter should only be used when there are more than one kind of client or the application use case involves multiple transactional resources. In other cases, the benefits of using Service Layer are hugely compromised by the constructing effects. | The Service Layer patter should only be used when there are more than one kind of client or the application use case involves multiple transactional resources. In other cases, the benefits of using Service Layer are hugely compromised by the constructing effects. | ||
Revision as of 11:17, 6 October 2008
The definition for the Service Layer Pattern is “defines an application’s boundary with a layer of services that establishes a set of available operations and coordinates the application’s response in each operation”.
A service layer always defines the application’s boundary and the responsibilities from the client’s view point. The business logic are usually be considered as domain logic and application specific logic. When application logic and domain logic are mixed together, the result domain logic class becomes less reusable and hard to maintain or extend. The Service Layer can be used in this kind of situation to factor the application specific logic our from the domain logic.
There are two ways of implementing the Service Layer Pattern. One is the domain façade approach which builds a façade to invoke the business logic provided by the domain logic classes. Another approach is named the operation script approach, which builds a layer of classes for the application logic with the encapsulated business logic from those business logic classes.
When to Use It
The Service Layer patter should only be used when there are more than one kind of client or the application use case involves multiple transactional resources. In other cases, the benefits of using Service Layer are hugely compromised by the constructing effects.
