Many organizations start with an ad-hoc methodology for their IT infrastucture, and over time it acts as a point-to-point system. If we define transaction costs as the sum of all costs over time for development, maintenance and operation, then a P2P infrastructure resembles an exponential (n-squared) curve against organization size (as a proxy for total complexity).
J2EE introduces a centralized hierarchy and standardized APIs, which impose higher startup costs, but which increase at a flatter rate for larger organizations.
Service Oriented Architecture introduces a formal message backplane which functions as a mediator, and it's probable that SOA's cost curve is flatter than J2EE. This graph shows how framework cost might be associated to organization size:
For small organizations, the cost-effective choice might be LAMP or simple programming tools.
The choice for mid-sized companies is probably J2EE.
Although SOA and J2EE aren't direct competitors, SOA has no dependencies on a J2EE infrastructure. For larger companies, it's certainly possible that alternate implementations of SOA might replace marginal J2EE installations.
( Oct 23 2006, 03:27:27 PM EDT ) Permalink Comments [1]
Posted by private student loan on February 20, 2007 at 10:24 AM EST
Website: http://del.icio.us/private_student_loan #