It’s just data

Robust, fluid transactions

Jon Udell: I wonder about this a lot, lately, when thinking about the differences between LAMP (Linux/Apache/MySQL/Perl|Python|PHP) and .NET/COM+ or J2EE/EJB. Where's the inflection point between these two styles? When you harden an architecture for robust transactions, how do you preserve the fluidity that the agile enterprise requires?

It's pretty dry reading, but my belief is that the answer lies in here, though a much better place to start is in the introduction.  The first implementations of this spec likely are going to focus on atomic transactions which work well when you control both ends of the wire, but the life doesn't work that way.

Saving for later......

Excerpt from Archipelago at

I'm not sure if LAMP or J2EE or dotNET, and hence WS-Transaction, which is a layer above this thirty year old architecture, will lead to a more agile enterprise.

I think we need a rethinking of databases, messages, and coordination. Some thoughts are at, but more will follow.

Posted by Patrick Logan at

Appropriate use of J2EE/EJB

An oft-heard complaint, echoed recently by Annrai O'Toole, is that J2EE app servers are oversold: The J2EE vendors have done a fantastic job of convincing the world that you can't run a line of Java unless it runs inside a J2EE container. This is...

Excerpt from Jon's Radio at

Add your comment