Service Oriented Architecture

Abstract
Service Oriented Architecture (SOA) has been proposed as a way to model distributed software development that surpasses the traditional Distributed
Object Architecture (DOA) practices in many areas. However, no empirical studies have been conducted toverify the claimed benefits. This study is a first attempt at presenting empirical evidence regarding the benefits of SOA. It is a comparison between traditional DOA using the EJB technology and SOA using Web Services. These two technologies were compared on the
basis of code size (LOC) and development time. The
results show that, as a whole, the subject application
was faster to develop using the SOA method. However,
the LOC developed with the SOA method was almost
twice that developed with the EJB method.
Key Words: SOA, Web Services, EJB, SOA
experimentation
1. Introduction
The traditional Distributed Object Architecture
(DOA) used in building multi-tier Web based
applications can reach its limit when highly distributed
heterogeneous systems need to interoperate. Some
modern web applications are using a new computing
model where services are treated as self-contained
modules that can be advertised, discovered, composed,
and negotiated on demand.
Service Oriented Architecture (SOA) is a model for
designing, building, and deploying distributed software
applications. It emphasizes loosely coupled design
approaches where disparate systems, with different
computing platforms, can collaborate without major
changes to their existing core architectures.
Despite wide industry and academic attention, no
evidence has been presented to substantiate the claimed
benefits of SOA. IT managers are faced with anecdotal
evidence and strong commercial campaigns. Therefore,
empirical studies are needed to evaluate the value of
SOA.
This paper reports on a first attempt to attain
empirical evidence regarding the benefits of SOA. It is
a comparison between traditional DOA using the EJB
technology... [continues]

Read full essay