Skip to main content

Mark Little

Mark is Director of Standards and a Development Manager at JBoss. Prior to this he was chief architect for Arjuna Technologies, a spin-off from Hewlett-Packard specializing in distributed transaction and messaging solutions for J2EE and Web Services. Prior to Arjuna, Mark was a distinguished engineer for HP, where he lead the transactions team. Mark has published several books in the areas of Java and regularly publishes in conferences, workshops and journals. He's also active on various standards bodies, including JCP, OASIS and W3C.


marklittle's blog

Transactions are your friend

Posted by marklittle on March 2, 2006 at 1:25 PM PST

After having been doing this for 20 years, I can say that transaction processing has got to be one of the most difficult middleware components to persuade developers to use.

When and why are interoperability fests useful?

Posted by marklittle on February 1, 2006 at 3:09 AM PST

The world of Web Services has thrown up a range of various interoperability

Transactions and recoverability: what they mean to your applications

Posted by marklittle on May 11, 2005 at 12:53 PM PDT

The main problem that I hear about using transactions is performance. In order to guarantee atomicity in the presence of failures, the coordinator must first execute the two-phase commit protocol across all participants to achieve consensus.

A session & context concept for Web Services

Posted by marklittle on May 7, 2005 at 2:44 PM PDT

One of the common features of all middleware systems is support for the session concept. You don't have to look far to see this: J2EE, CORBA and going back further to systems such as Emerald, Argus and Camelot. A session is a mechanism for correlating multiple messages in order to achieve some application-visible semantic.