Introduction to SOA

Point to Point Integration

• "Accidental"Architecture (Synchronous, Fine-grained, Not scalable, Many connections and data formats, Extremely difficult to manage, Expensive to maintain and extend)
• Hinders business change: new products, channels, suppliers, etc.
• Slow and expensive maintenance, No Reusability
• Expensive to Manage, Monitor and Extend
• Need realistic way to evolve new infrastructure and add value

Business processes become Agile when implemented as Services

Business Perspectives

• Simplification
• Elimination
• People
• Process Performance
• Measurement
• Simulation modeling
• Agility, etc.

BPMN Notation Representing a business process
with an expanded Sub-process

• Working Software
• Reliability
• Configuration Management
• Scalability
• Performance
• Reusability
• Speed of Delivery, etc.

Example: Process Implemented as Services

MOM - (Message Oriented Middleware)

• Easy Inter-Operability
• Easy Common Data Model for integration
• Robust Process Management
• Scalability and High-Availability
• Distributed services management Real time configuration changes
• Reusability of Components & Services in an effective IDE
• Portable Adapters
• Cost, Speed, Quality & Control

Example: Process Implemented as Services

The Integration Broker Iceberge

• Suffer from incomplete and competing standards definition that might not ensure easy interoperability across different implementation
• Interoperabilty
  • SOAP
  • Only binding for HTTP; no bindings for SMTP, JMS
  • "SOAP encoding": XML Objects
  • RosettaNet, EDIINT: no SOAP
  • SOAP 1.1 1.2 (W3C)
• WSDL: RPC/Encoded vs. Document/Literal
• Do not offer a complete package but provide only the functionality of access and invocation leaving majority of the development work to the user
• Business Semantics -Orchestration & Choreography
• Security
  • HTTPS is not enough
  • No agreement regarding attachments
  • S/MIME in RosettaNet and EDIINT
  • Single Signon
• Transactional Integrity
• Reliable Asynchronous Message Handling
  • WS-Reliability (IBM, MS) vs. WS-ReliableMessaging (OASIS)
• Transformation Services