Hello,

I am working on a pre-existing project that presents a situation I never thought of. The service layer has hundreds of methods, so its broken out into a couple dozen service layers classes, each with entry points that the Web.UI makes calls to. Is this compliant with standard Enterprise Patterns ? I always thought the Service Layer should be a single class.

Thank-you.

If you take a look at the book's case study you'll find exactly the same setup. The service layer is one separate class library that contains many service classes. Each is described by its interface e.g. the IProductCatalogService on page 474. Conceptually, each service provides methods related to a certain area of the domain. For example, the BasketService class on page 539 provides methods to handle requests for obtaining, creating or modifying the shopping basket.