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.

WS-TX 1.1 standard announcement

Posted by Mark Little on May 23, 2007

Sections
Architecture & Design,
Enterprise Architecture
Topics
Transactions Processing ,
SOA ,
Web Services
Tags
WS-BusinessActivity ,
WS-AtomicTransactions ,
Transactions ,
WS-Coordination ,
Web services
We announced in April that the members OASIS had finished voting to accept WS-TX 1.1 (WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity) as a standard. The official announcement took a little while to come out, but it's now official. As the announcement states:
OASIS, the international standards consortium, today announced that its members have approved Web Services Transaction (WS-Transaction) version 1.1 as an OASIS Standard, a status that signifies the highest level of ratification. WS-Transaction describes an extensible framework for providing protocols that coordinate the actions of distributed applications. Such coordination protocols can be used to support a wide variety of applications that require consistent agreement on the outcome of distributed transactions. WS-Transaction is offered on a Royalty-Free basis, as provided under OASIS policies.
Eric Newcomer, CTO if IONA Technologies and co-chair of the committee had this to say
"Web services increasingly tie together large numbers of participants to form distributed applications. The result can be extremely complex. WS-Transaction gives developers the framework they need to build reliable, distributed applications."
On his blog, Eric shows how long it has taken in some respects to get to this stage. We've covered the history in more depth before, but transactions are a very important service in all computing environments, so it is good to see them finally standardised in Web Service. Ian Robinson, from IBM and the other committee co-chair recognized the history behind WS-TX:
"The technical committee recognized that there is no single transaction model appropriate for all use cases, and so WS-Transaction defines an extensible coordination framework that accommodates classic two-phase-commit, as well as more relaxed forms of transactions with isolation behavior appropriate in loosely-coupled systems."
The technical committee is looking at whether there is any further work to be done in the area. If not, it will probably be placed into maintenance mode. There was some mention about looking at whether similar efforts from WS-CAF could be leveraged into WS-TX, but there has been no discussion in the group about this for over a year. Since WS-CAF has just closed down, this now looks unlikely.
  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

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.