I wrote Saving J2EE about six months ago. At that time, I omitted a set of strategies in the conclusion, but my first question was "should we even try to save J2EE?"
My answer now is "probably not".
J2EE solves a set of transaction-related problems across large systems. A rehash of J2EE will probably fix many poor implementations (I did my share of those) and extract some value from the remaining marginal set of those transaction issues.
But the more I read on Service Oriented Architecture, the more I think that it solves a different set of transaction issues in large systems, for a net gain of more value. For instance, the top level structure of SOA is a simple pattern -
The Mediator is a basic transaction-cost-cutting pattern. Coupled with adapters, I suspect that total transaction cost for large organizations is very low, almost certainly lower than J2EE's model, because I can't even work out a simple J2EE comparison model without some complex pieces.
A simple mathematical scheme could do a rough transaction count for both models, and compare them against different implementation sizes. I strongly suspect that SOA will be substantially lower across a wide range of larger organization sizes.
I'm about 90% sure that "Saving J2EE" is correct; market demand for J2EE is topping out and it will be measurable in sales terms by the end of 2007.
( Dec 17 2005, 01:09:42 PM EST ) Permalink Comments [1]
Posted by credit card terminal and processing on February 20, 2007 at 10:49 AM EST
Website: http://del.icio.us/credit_card_terminal #