Home > Articles > Web Services > SOA

SOA Pattern (#12): Service Layers

The Service Layers design pattern attempts to standardize the way services are designed within a service inventory by organizing services into logical layers that share a common type of functionality. By structuring the service inventory around common types of functionalities, this design pattern eases the evolution of services and reduces their governance burden.
Like this article? We recommend

Like this article? We recommend


A service can be designed in a manner that it contains both the reusable logic as well as the process-specific logic. Similarly a service may contain logic that interfaces with legacy systems along with process-specific logic. Keeping these different types of logics within the same service severely restricts the evolution of the service and results in a service inventory that contains non-standardized services as services delivered by different project teams would contain a different blend of logic. By creating a service that contains a combination of agnostic and non-agnostic logic, the reusability potential of such a service is greatly reduced, which goes against the guidelines of the Service Reusability and the Service Composability principles. In order to standardize the way different capabilities are added to the services, the Service Layers pattern introduces a logical grouping of services, whereby the same group of services share a common type of functionality. By restricting the service to a particular type, the service can only encompass a particular type of functionality. This not only helps in easy evolution of the service but also helps to reduce the redundancy levels of the solution logic.

The division of a service inventory into logical groups is somewhat analogous to the different layers created in a typical software program, that is data, business and user interface layers. By dividing the software into a set of layers, the components or classes encompassed by a layer need to be designed in a particular manner so that they manifest the overall characteristics linked with that layer. This helps in bringing a structure to the software program and makes it easy to modify a layer without negatively impacting other layers. The same principle applies in case of service inventory where the application of the Service Layers pattern results in a more manageable service inventory as each layer consists of services that contain a specific type of functionality; hence the impact of change within a service remains minimal as long as it fulfills its contract.

Another important benefit related to creating different service layers is that it gives a bird’s eye view of the different types of functionality offered by the service inventory. This is something that could be of interest to the non-technical business IT team members because by tagging a service that it belongs to a particular layer, it inherits the characteristics of that layer and hence it becomes easier to understand the overall type of functionality provided by the service.

Normally a service inventory would be grouped into a set of task, entity and utility layers; however, it is quite important to understand that these three types are by no means cast in stone. In fact what is required is to first perform an analysis of the different types of functionalities contained within a service inventory and then to choose the most suitable service models that best represent the different kinds of functionalities contained within the service inventory. It should be noted that at least there should be two types of groups of services within an inventory: one that contains agnostic logic and the other that contains process-specific logic. In order to arrive at a set of layers, or more precisely which service models to choose, the creation of a service inventory blueprint is required. From the service inventory blueprint, the intended functionality enclosed by all candidate services can be analyzed to select the different types of service models required to best represent the broader types of functionalities within the inventory blueprint. This also gives an opportunity to move the candidate service capabilities in between different service candidates, belonging to different layers, in order to bring standardization to the design of the actual services so that a service only contains the right type of logic as dictated by its containing layer.

The application of the Service Layers pattern only establishes the different types of service layers that an inventory should contain; however, in order to actually design the services that make up the relevant layer, the Process Abstraction, the Entity Abstraction and the Utility Abstraction design patterns could be applied. It should also be noted that the categorization of a service inventory into different types of layers needs to be revisited as more and more SOA projects are delivered. This is because the categories established right at the start of an SOA initiative may only represent a subset of the business processes and as more and more business processes are automated, the service inventory increases in size and can result in new types of functionality that were not originally deem to be required. This means that until a service inventory becomes mature, a provision for a change in the categorization of the service inventory needs to be kept in mind. Once enough services exist in the service inventory so that they represent a meaningful part of the business domain, the established service models can be implemented as enterprise standards that can be applied to other or future service inventories.

The Service Layers pattern is one of the fundamental design patterns that helps to structure the service inventory in a manner that promises reduced governance overhead; however, its application requires performing top-down service-oriented analysis and design which demands increased resources both in terms of time and efforts.

The SOA Pattern of the Week series is comprised of original content and insights provided to you courtesy of the authors and contributors of the SOAPatterns.org community site and the book “SOA Design Patterns” (Erl et al., ISBN: 0136135161, Prentice Hall, 2009), the latest title in the Prentice Hall Service-Oriented Computing Series from Thomas Erl (www.soabooks.com).

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020