Home > Articles > Software Development & Management

Web Services Part 2: Current Technologies

Continuing his discussion of current technologies that lead to full web services, Alex Nghiem explores the advantages and limitations of distributed computing, component-based development (CBD), HTML, and XML.
Placing special emphasis on a comprehensive approach combining organization, people, process, and technology, Harris Kern’s Enterprise Computing Institute is recognized as one of the world’s premier sources for CIOs and IT professionals concerned with managing information technology.
Like this article? We recommend

Part I of this series identified market conditions and some fundamental problems in enterprise software development (reuse and interoperability). We listed several existing technologies (object-oriented technology, distributed computing and thin clients, component-based development, HTML, and XML) and discussed the first one, object-oriented technology, to see how it addressed the issues. This and future articles will cover the remaining technologies in this list and progress to our primary topic, web services.

Distributed Computing and Thin Clients

Client/server development was at the forefront of the PC revolution. As user demands became more sophisticated and as programs grew in complexity, software developers devised more techniques for handling this complexity. Client/server development is characterized by a client application that handles much of the processing logic and a server program that processes database requests. Unfortunately, this architecture requires expensive client machines because all the processing happens on the client side. For programs to be deployed to a larger audience (that is, the web), it's not feasible to always expect the users to own high-end client machines. Hence, alternative methods are needed for designing applications.

Distributed computing refers to the broad practice of implementing applications in an n-tier architecture (n being three or more). The new tier is often referred to as the middle tier and houses the business process logic that should ideally be independent of the underlying database logic and user interface. (The business logic is usually written in the form of classes or components; components are covered in the next section.)

To fully leverage the investment in business logic, the functionality can be shared by multiple applications. To accomplish that goal, the middle tier provides a set of infrastructure capabilities to handle issues such as session management, resource management, concurrency management, messaging, and so on. Rather than implementing these sets of capabilities for every business application, it's common practice to purchase them in the form of an application server. Popular examples of application servers include BEA WebLogic Server, IBM WebSphere, etc. With an application server, developers can then focus on writing business logic rather than infrastructure code.


The language in which the business logic is written depends on which application server is used. As an example, JavaSoft defines the J2EE standard; using a J2EE-compliant application server requires that the business logic be written in Java (or C++, since Java programs can call C++ programs).

The client program communicates with the application server, which in turn communicates with the database. Multiple copies of the application server replicated among the many physical servers can provide load balancing and resource pooling, which prevent performance degradation and improve stability as the numbers of users escalate.

One of the central ideas of distributed computing is the concept of location independence. That is, if a client program makes a request, it shouldn't matter whether the receiving program is on the local machine or remote machine(s). This location independence is often provided by a naming service—a mechanism for the calling program to find and then bind to the receiving resource, which can be an object, program, page, and so on. The naming service may or may not be part of the application server.

Since the business logic is centralized on one or more servers, rather than distributed across many client machines, as is the case with a client/server architecture, this architecture provides the following benefits:

  • With the processing happening primarily on the server, the client machine is relegated to mostly a display device. Consequently, the client machine can be a lower-end machine because it's primarily responsible for displaying information rather than processing business logic (which is more CPU-intensive). This in turn reduces hardware purchases and OS dependencies (of course, we now have browser dependencies).

  • Deploying or updating an application doesn't require installing an application on each user's machine. The client machine often requires only a browser; the middle tier executes the business logic and the client machine simply displays the data. Hence, distributed computing often leads to a thin client architecture.

  • There are potentially fewer compatibility issues because many of the software installations and updates are on the server side, which can be handled in a centralized fashion.

However, nothing in life is free, which means that there are significant disadvantages to distributed computing and thin clients as well:

  • Building distributed applications is notoriously more difficult than building client/server applications. Debugging and tuning these types of applications are not trivial because there are more points of failures and errors.

  • The user interfaces on thin client applications are rarely as sophisticated as those on client/server applications. These UIs tend to be browser-based, and the browser imposes limitations on what's possible; whereas a client/server application can interact directly with the native windowing environment and the native operating system as well. As an example, few (if any) thin client applications support a sophisticated drag-and-drop metaphor, but this is a very common metaphor in most client/server applications.

  • Performance tends to be slower on a thin client application than on a client/server application. With a client/server application, the client application can perform sophisticated operations without depending on the server, whereas a thin client application tends to be able to display only the results of processing that happened on a server. The processing is typically initiated by the client to the server over a network. The network latency tends to be the bottleneck of a thin client architecture, whereas the processing power of the client machine tends to be the bottleneck in a client/server architecture.

Even with these limitations, a thin client architecture is the more viable architecture for applications that have to be deployed to a large audience that wants minimal installations and hassles, as is the case with web applications.

As we'll show later, web services share many of the advantages of a thin client architecture (location independence and centralized management), but such challenges as performance tuning, debugging, and a consistent GUI are potentially magnified.

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