Category Distributed Internet Service oriented Architecture

Architecture
Application Tightly Coupled: at design time, Loosely Coupled: SOA still rely on
Logic the expected interaction components but the use of Web Services
components will have with others (i.e., standardized interface and open
is taken into account – so much so communications framework) supports a
that actual references to other composition model, allowing individual
physical components can be services to participate in aggregate
embedded in code. It is efficient assemblies.
in that little processing is wasted Document-Style Data Exchange: web
in trying to locate a required services communicate with SOAP
component but the embedded messages which rely primarily on
coupling leads to a tightly coupled document-style messages which are
component network. structured to be as self-sufficient (meta
information, processing instructions and
Parameter-based Data policy rules) as possible which results in
Exchange: components provide less individual transactions.
methods that, once invoked, send
and receive parameter data. Re-use: fosters re-use and cross-
application interoperability by promoting
Re-use: emphasized but rarely the creation of solution-agnostic services.
achieved due to tight-coupling.
Application Inter-Component Inter-Service Communication:
Processing Communication:  Message-based communication
 DIA promotes the use of that involves the serialization,
proprietary communication transmission an de-serialization
protocols such as DCOM of SOAP messages containing
and vendor implementations XML payloads. (Despite
of CORBA for remote data improved parsers and hardware
exchange accelerators, SOAP still lags
 supports the creation of RPC communication.) Document
stateful and stateless and message modeling
components that interact conventions and the strategic
with synchronous data placement of validation logic are
exchanges (asynchronous important factors that shape the
supported by some transport layer of SOA.
platforms but rarely used).  Although synchronous
communication is supported,
asynchronous patterns are
encouraged, as they help
minimize communication.
 Further supporting the
statelessness of services are
various context management
options that can be employed,
such as WS-Coordination and
 WS-BPEL
Technology There is no governance of the XML data representation and the Web
technologies used by DIAs (e.g., Services technology platform
components, server-side scripts,
raw web technologies such as
HTML and HTTP)
Security Traditional delegation and WS-Security Framework: emphasize the
impersonation approaches as well placement of security logic onto the
as HTTP encryption messaging level. SOAP messages
provide header blocks in which security
logic can be stored which helps to
preserve individual autonomy and loose
coupling between services as well as the
extent to which a service can remain fully
stateless.
Administratio  Maintaining component-  Require additional runtime
n based applications administration since problems
involves keeping track of with messaging frameworks
individual component (especially when working with
instances, tracing local and asynchronous exchange patterns)
remote communication can more easily go undetected
problems, monitoring than with RPC-based data
server resource demands exchanges since so many
and standard DBA tasks. variations exist as to how
 DIA introduces the Web messages can be interchanged.
Server as the official first  WS-* extensions for messaging
point of contact for clients frameworks have yet to reach
so is must therefore be maturity
designed for scalability.  UDDI helps with resource
 RPC-based data exchange management and service
generally requires a description
response from an initiating
component and an
exception handling routine
is employed.