Q

Is there progress in maintaining Web service transactions across different transaction servers?

This Content Component encountered an error

Is there progress in maintaining Web service transactions across different transaction servers?

The XA standard defines a mechanism to coordinate transactions across multiple transaction managers, but I'm skeptical about using 2PC technology across loosely coupled application systems. I'm of the opinion that we need to devise a new approach to manage loosely coupled transactions. There is such an effort underway at OASIS (www.oasis-open.org), called Business Transaction Processing (BTP). You might find this article on BTP enlightening.

But BTP is still a future. There are no implementations today.

The way you solve it today is to build transaction recovery into your applications. If part of your extended transaction fails, you must manually undo the other parts that have been committed. These "undo" methods are known as compensating transactions. It's not pretty, but it's the only viable approach today.


This was first published in February 2002

Dig deeper on Simple Object Access Protocol (SOAP)

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide

SearchWinDevelopment

Close