What is SOA?

IT architecture for request - reply applications Application functions are modularized and presented as services Services are loosely coupled

Service interface is independent of the implementation

SOA Slides
Raghu Kodali http://www.nejug.org/2005/include/SOA andWebServices.ppt

Service-oriented architecture (SOA) definition

A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed.
(http://www.service-architecture.com/web-services/articles/serviceoriented_architecture_soa_definition.html)

Many other definitions can be found

Characteristics of SOA
Services have platform independent, self describing Composable interfaces (XML) Messages are formally defined Services can be discovered Interoperable SOA Re-Usable Services have quality of service characteristics defined in policies Loosely Services can be provided on Coupled any platform

Why SOA? The Cruel Reality

Application Screen Scrape Message Queue Download File Application Transaction File Screen Scrape Sockets Application ORB Message Application Message Transaction Queue File Application Screen Scrape CICS Gateway Download File APPC Application Message Queue Application Screen Scrape Transaction File Application RPC ORB

Application

Sockets

Download File

CICS Gateway

Transaction File Application

Message

APPC

RPC

Source: Gartner

Why SOA?
Respond to business changes Address new needs with existing applications Unlock existing application investments Support new channels & complex interactions Support organic business
Oracle Financials Standard Interface Custom Order Application Standard Interface New Web Application Standard Interface

New Supply Chain Management Application (Business Process or Composite Application) Standard Interface Siebel CRM Standard Interface Mainframe HR Application Standard Interface .NET Inventory Application

Anatomy of a Service
New Service
Service Consumer Wrapped Legacy
Interface Proxy

Composite Service
Service Interface Service Implementation

Service Communication
Communicate with messages No knowledge about partner Likely heterogeneous

Service Consumers

Service Producers

Service Platform
Service Consumers

Service Delivery Bus

Change

Service Rules & Config Service Interfaces and Service Implementations

Service Reporting & Mgmt

Control

Benefits of SOA
Better reuse

Build new client functionality on top of existing Business Services Make changes without affecting clients Changes/Versions are not all-or-nothing

Well defined interfaces

Easier to maintain

Better flexibility

Services Communicate With Messages

Providing reliability and security to messages Sending messages across consumers and producers Service Orchestration

Service Consumers

Service Producers

Basic Web Services

UDDI Registry
Points to description

WSDL
Points to service Describes Service

Finds Service

Web Service Client

(J2EE, .NET, PL/SQL )

SOAP

Web Service
(J2EE, PL/SQL, .NET,C/C++, Legacy )

Invokes with XML Messages