Home > Articles > Web Development

  • Print
  • + Share This
This chapter is from the book

7.3 Service Loose Coupling

In a service-oriented environment, components can be coupled at a number of different levels. Coupling can occur at the level of the service contract, the service implementation logic, or the underlying technology platform the service is running on if a service consumer is coupled with a particular service. In general, SOA promotes the notion of decoupled systems by which the parts of a service-oriented solution are as decoupled as possible. Reducing the dependency of one part on another allows one area, such as a service or an aggregation, to be changed without requiring changes to other areas.

The following design characteristics are helpful in the creation of decoupled systems:

  • separation of contract and implementation
  • functional service context with no dependency on outside logic
  • minimal requirements for the service consumer

When service logic is implemented in Java and executed in a JRE, a coupling is created between the logic and the underlying technology platform, Java. Additional dependencies arise when Java EE is used as the hosting platform. For an in-depth explanation of the variations of positive and negative coupling, see Chapter 7 in SOA Principles of Service Design.

Separation of Contract and Implementation

The separation of a service contract from its implementation is a key characteristic of service-oriented design that was first established as part of the definition of remote procedure calls and then in object-oriented programming. The interface of a component is exposed to a point that allows other logic to invoke this component, but no details about the implementation are added. Changes to the implementation can then be made without affecting the client. SOA took this concept further by establishing the notion of a standards-based contract. For example, the service interface can be expressed in a programming language-neutral way to allow for the integration of logic written in different languages and running on different platforms.

The choice of programming language can be exposed in the service contract. In the context of a SOAP Web service from the Top-Down vs. Bottom-Up section, a common approach is to generate the service contract from existing Java logic. In JAX-WS, the wsgen tool can be used to generate a complete WSDL document, including the XML schema definition from an existing JavaBean or Java interface. However, the existing Java code may not be easily mapped into XML schema.

For example, assume that the public java.util.Hashtable<String, String> getTable(int i); method is part of an interface to be turned into a service. Using the wsgen tool to generate both the WSDL and XML schema definition from this interface creates the type definitions presented in Example 7.33.

Example 7.33

<xs:element name="getTableResponse" type="ns2:getTableResponse"
  xmlns:ns2="http://the.package/"/>
<xs:complexType name="getTableResponse">
  <xs:sequence>
    <xs:element name="return" type="ns3:hashtable" minOccurs="0"
      xmlns:ns3="http://the.package/"/>
  </xs:sequence>
</xs:complexType>
<xs:complexType name="hashtable">
  <xs:complexContent>
    <xs:extension base="ns4:dictionary"
      xmlns:ns4= "http://the.package/">
      <xs:sequence/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
<xs:complexType name="dictionary" abstract="true"/>

The result is a valid XML schema definition, although a Java Hashtable is exposed in the service interface which renders the schema not useful or usable outside of Java. The same is true for many other classes and interfaces in Java, which, while useful as part of the implementation, do not map well into XML schema and non-Java environments. Many of the more technically-oriented classes, including the members of the java.io package, fall into this category.

The use of internal, platform-specific information carried in a generic type is another aspect of decoupling the contract and implementation. For example, the name of a file usually stored as a string can be mapped into XML schema and added to a service contract. However, exposing file names on a service contract is considered poor practice, and revealing details of the service implementation to the service consumer should be avoided. The same holds true for names of databases, database tables, machine names, and addresses.

Using the reverse approach is another way of creating this coupling, particularly when generating a service logic skeleton directly from a service contract. In JAX-WS, the wsimport tool is used to create Java code skeletons representing a given WSDL definition. Despite being the recommended approach, be aware that the generated Java code is now tightly coupled to its contract, which prevents the code from being easily reused to serve other types of service contracts or updated versions of the current contract. In most cases, the tight coupling is acceptable because the logic is created for a particular contract and nothing else.

However, instances occur where service logic must be created for reuse despite changes to the underlying contract changes or the need to concurrently serve multiple versions of the same contract. The JAX-WS Provider API is equipped for such instances. In this model, the service logic parses the incoming message at runtime for dynamic processing with no direct dependency on the types and elements defined in the WSDL contract. Use of the JAX-WS Provider API is detailed in Chapter 8.

For a REST service, coupling the code to the service contract is inconsequential because generating implementation artifacts from a machine-readable contract, unless WADL is being used, is uncommon. Implementing a Web resource for a platform, such as JAX-RS, out of the box supports only a finite subset of Java classes that can be automatically mapped to appropriate content-types. For custom types not mapped automatically by the built-in content handlers, developers must provide implementations of javax.ws.rs.core.MessageBodyReader/MessageBodyWriter interfaces to map such types to a known set of resource representations or media types.

Independent Functional Contexts

Besides the direct compile-time of coupling services, consider the coupling of a service to its outside functional context. Service invocations happen as part of a business transaction or process to establish a context that effectively binds the services, which are invoked downstream, into an aggregated set. Having a set of services as part of the same process establishes a type of coupling between the services, a coupling that should always be top-down. Particularly when leveraging other services to fulfill functionality, a service implementation can be coupled with or have dependency on those services. However, the service should not have a dependency on any services at a higher level of the process hierarchy, or be coupled with the invoking service or with peer services.

For example, assume that a service offers Credit Check functionality. The service is implemented as a business process that invokes a number of other finer-grained services, such as Credit Lookup, Credit Eligibility, Update Profile, and Notification. All four downstream services are peers within the Credit Check business process. Service peers should have no dependency on each other, or be aware of or coupled with their upstream Credit Check service.

Services representing business processes, such as Credit Check and Maintain Customer Information, are decomposed into a set of fine-grained services to create a downstream dependency. A service should not introduce a dependency on another service that is higher level. For example, the implementation of the Update Profile entity service should not introduce any dependency on the Maintain Customer Information task service.

In Java, the same principles of downstream dependency hold true. Unwanted dependencies can be detected by examining the classes that are used by a piece of Java logic. Organizing classes into packages directly identifying the service and/or affiliated business process and ensuring that logically decoupled functions are not packaged together is recommended. A package name should be selected with consideration for possible reuse opportunities. For Web services, the same requirements for namespaces are used in the service contract.

Service Consumer Coupling

For SOAP-based Web services, a service consumer will often be tightly coupled with the service contract and not the implementation of the service being invoked. However, a looser coupling lessens the impact when the service contract changes.

Using the JAX-WS Dispatch API, service consumer logic can dynamically assemble a request message at runtime and manage any response messages. Additional effort is required to build service consumer logic that can build request messages that the intended service can process.

Another way of further decoupling a service consumer from the service is to insert an intermediary between the two. The intermediary, generally deployed as part of an ESB, can mediate the differences in message format and network protocol to further decouple the service consumer and service. Chapter 12 explores this further as part of its coverage of ESBs.

  • + Share This
  • 🔖 Save To Your Account

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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