InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

OASIS WS-Transaction (almost) a standard

Posted by Mark Little on Jan 24, 2007

Sections
Architecture & Design,
Development,
Enterprise Architecture
Topics
SOA ,
WS Standards ,
Interop ,
Transactions Processing
Tags
Web services ,
Standardization ,
WS-Coordination ,
ACID ,
WS-BusinessActivity ,
WS-AtomicTransactions

The OASIS WS-TX technical committee held a  face-to-face meeting last week at IBM Hursely. This is likely the last such meeting prior to final standardisation of WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity. It has been a long struggle to get here, dating back to extended transaction work at the OMG, a first attempt at Web Services standardisation via BTP and OASIS WS-CAF (where there is a lot of overlap due to history). This meeting was primarily just making sure that all of the i's were dotted and t's crossed and getting agreement to progress to OASIS standard; all of the heavy work had been done over the past 12 months.

This is an important step for enterprise Web Services deployments for a number of reasons:
  • WS-AtomicTransaction defines a traditional ACID transactions model, based on two-phase commit (2PC). Many people believe that 2PC is not right for the loosely coupled nature of Web Services and they'd be right. However, this overlooks the other important aspect of Web Services: interoperability. Interoperability between existing vendor implementations is key for many transaction processing deployments, particularly those that have grown via acquisitions of heterogeneous technologies. This has been a transaction processing holy grail for many years.

  • WS-BusinessActivity provides a forward compensation model, much more appropriate for loosely coupled, long duration interactions. This latter model will probably have slower take-up than WS-AtomicTransaction, but it should become more important over time.

Once we finalise WS-Security and WS-Reliable Exchange we'll finally be able to do secure, reliable and transacted Web Services in a standard manner.

  • This article is part of a featured topic series on SOA
Agree wholeheartedly by John Harby Posted
Unbelievable by Eirik Maus Posted
Re: Unbelievable by Mark Little Posted
  1. Back to top

    Agree wholeheartedly

    by John Harby

    I definitely agree that this is a huge milestone. I recall Sven Frolund, Kannan Govindrajan, myself and others at HP labs discussing the compensation model back in the late '90's. Having participated with Mark and the others on this TC, I would like to state that the TC was conducted with the utmost formality and professionalism and for myself was certainly a learning experience in how such things should be handled.

  2. Back to top

    Unbelievable

    by Eirik Maus

    Have anyone heard of any actually interoperable implementations yet?

  3. Back to top

    Re: Unbelievable

    by Mark Little

    You mean apart from the interoperability work that many of the vendors within the TC did as part of developing the specification? jboss.org/jbossBlog/blog/mlittle/

Educational Content

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.