Home > Articles > Web Services

Extreme Web Services: Transactions

How do you handle transactions in an unreliable Web world? Kennard Scribner and Mark Stiver present opposing viewpoints so that you can formulate your own opinions and choose the approach that best fits your situation.
This article is excerpted from Chapter 9, "Extreme Web Services," of Applied SOAP: Implementing .NET XML Web Services, by Kenn Scribner and Mark Stiver, Sams Publishing (ISBN 0672321114).
This chapter is from the book

Over the last several years, transactional programming has regained momentum because developers have recognized its importance in Internet computing. You can see this re-emergence in the products that you use. Microsoft released MTS and eventually COM+, both providing a robust environment for transactional computing. Even Java2 Enterprise Edition (J2EE) supports transactions through mechanisms such as entity beans. Transactions simply make systems more dependable, and that's certainly a goal that we all try to achieve.

So how do transactions fit into the Web Service paradigm? This section takes a look at two opposing approaches to distributing transactions over the Web.

Transaction Authority Markup Language (XAML)

Traditional transactions use a Transaction Authority (TA) to coordinate the orchestration of committing data changes or rolling back data to its original state. This is a common design pattern that has existed for many years.

Extending this functionality to the Web Service model presents several challenges. The most significant challenges are these:

  • A mixed-vendor environment

  • Distribution across the Web

  • Nonstandard, non–Web-based protocols

XAML intends to solve these problems by defining a transactional language, interface, and semantics using XML and other industry-accepted protocols such as SOAP.

At this time, the XAML specification is not currently available, but you can find a whitepaper on the topic at http://www.xaml.org.

The opposing methodology to XAML is based on data reconciliation using messages and validation, as presented in the next section.

Applying Transactions to Web Services

The idea is simple: Because developers currently use transactions to improve software dependability, it makes perfectly good sense that you would try to apply transactions in applications that are distributed across the Web, where potential for failure is extremely high.

Unfortunately, there is one difference—the issue of trust. Do you want your Web Service to be dependent upon some code that you know very little about?

Anyone who was fortunate enough to see the "Autonomous Computing" presentation by Pat Helland (an architect on the SQL Server team and transaction expert) at Microsoft TechEd 2001 is probably rethinking his stance on Web transactions.

The basic premise is: Independently controlled systems cannot and will not trust outside systems. Yet independent systems make up the fabric of the Internet. So how can you possibly manage transactions across Internet-distrusted systems? The proposal is that you can't!

Consider the case of a travel agency portal. The agency's system is designed to schedule airline and hotel reservations for a customer. The standard approach is to design the system so that an airline ticket and a hotel room are booked either successfully or not at all. One without the other is probably of little use to the customer. But to coordinate a transaction across the travel agency, airline, and hotel, they all need to trust one another.

Autonomous computing defines a design pattern that suggests that each independent entity in a computing relationship has private data that cannot be directly manipulated by other entities. Instead, outside entities must request that data be changed. Each request is authenticated, carefully validated, and either used or rejected. Remember that transactions increase the coupling between systems, and Web Services, by nature, should represent very loosely coupled systems.

Your service might choose to use standard transactions internally, but these transactions should never leave the walls of your system. When your service wants to share information to an outside entity, a snapshot of your data can be timestamped and then shipped out. By timestamping, you have stabilized the data, thus guaranteeing the accuracy of the data at some particular instant in time. Realize, of course, that snapshots of data increase in their staleness as time goes on. In other words, it will be easier to process requests that are based on fresh snapshots rather than to process those requests that are based on old snapshots.

The final piece to the puzzle is that your service also must provide ways to undo any changes that were made in previous requests. In the travel agency portal case, the airline and hotel services might each provide a way for reservations to be canceled. So, if a hotel room cannot be found, the customer would have the choice of keeping the flight and finding alternate housing or simply canceling the airline reservations.

The moral of the story is this: If you are building a service that will be used only within a trusted environment, you might have good reason to extend transactions to clients of your service. But any service that will be used on the Web should avoid exposing transactions and follow the stated guidelines.

Transactions are a hot topic in the Web Service arena, and they play an essential part in building dependable systems. This is clearly an area of Web Services that needs more thought.

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