SOA-05: Building an Enterprise SOA Using ESB

1
SOA-05 Building an Enterprise SOA Using ESB

• Dave Chappell
• Vice President Chief Technology Evangelist,
  Sonic Software

2
Sonic Software
Inventor and Leading Provider of the Enterprise
Service Bus (ESB)

• Recognized Inventor of the ESB the foundation
  of a SOA
• Enterprise messaging (1 JMS product)
• Major Standards Contributor/Influencer
• Established 700 Customers, 40 OEM/ISV
  partnerships
• Extensive SI Partner Support
• Independent Operating company of
• Progress Software (NASDAQ PRGS)
• 363M sales, over 180M in cash
• Consistent double digit revenue and
• profit growth
• Distribution in 65 countries
• 24x7 world-wide support
• Experienced Enterprise projects deployed in
• - Finance Banking
• - Telco
• - Retail
• - Government

3
Sonic Customers
4
Processes are fragmented
Applications deployed in different departments
and business units become silos of data and
process.
How can I flexibly incorporate data and process
from across the enterprise?
5
Enterprise SOA Vision
Idealized world where data and process flows
naturally
PORTAL SERVICE
USER-DEFINED SERVICE
BATCH SYSTEM
APPLICATION SERVER
RELATIONAL DATABASE
PROCESS SERVER
LEGACY APPLICATION
By 2008, Gartner predicts that SOA will be a
prevailing software-engineering practice, ending
the 40-year domination of monolithic software
architecture
6
Scope drives architectural considerations
SOA infrastructure requirements

• Heterogeneity
• Span new service-enabled applications as well as
  existing applications
• Scalability
• Provide the performance expected of enterprise
  systems while easily accommodating changes in
  demand
• Availability
• Isolate applications from faults resulting from
  server and communication failures

• Distribution
• Processes will interact with services spread
  across an organization, and between organizations
• Flexibility
• Allow the organization to change processes,
  rules, data mapping and relationships between
  applications with minimal effort and disruption
• Visibility and control
• Manage and monitor the infrastructure as well as
  the processes and services deployed within it

7
Web Services
Standard Interfaces are Major Step Forward

• Hiding implementation details enables reuse
• XML-based data easily exchanged
• Designed for remote access, across heterogeneous
  platforms
• WS-RM standardizes reliable interoperability

SOAPHTTP
WEB SERVICESINTERFACE
8
Web Services
But Have We Solved The Whole Problem?

• How do you deploy, monitor and control the
  services or their interactions?
• How do you connect legacy systems with different
  protocols
• How to your mediate data formats and interaction
  models
• How does it scale it up?

SOAPHTTP
WEB SERVICESINTERFACE
Web services provide transport, but, dont
support differing protocols, the need for
routing, data transformation, remote deployment,
or overall monitoring capabilities.
9
A new approach
Combines the best of previous technologies
10
A new approach
Combines the best of previous technologies
RELIABLE COMMUNICATIONS
ENTERPRISE SERVICE BUS SOA INFRASTRUCTURE
SERVICE MEDIATION
SERVICE HOSTING
SERVICES
11
To form an ideal SOA infrastructure
Map and bind services, processes, and IT assets
ESB makes it easy to connect, mediate, and
control services and their interactions
12
Enterprise Service Bus (ESB)
The Foundation for Enterprise SOA

• Distributed services architecture
• Enterprise-grade communications backbone for
  reliable messaging
• Intelligent routing and content based routing
• Process coordination
• Flexible security framework
• XML transformation
• Management

13
Global reach
Global deployment and process, local autonomy
Any number of services
Any numberof locations
Any numberof processes
Any scale
14
ESB Architecture
Business Process, Services, Network Topology
London
Chicago
Tokyo
Svc1
Svc2
Svc3
Secure, Scalable, Message Broker Clustering,
Continuous Availability
15
Enterprise Grade Messaging Backbone
A way to reliably connect services across domains
16
Forming a Distributed Services Bus
Used to reliably connect service containers
17
Parallel processing / load balancing
Services can be independently scaled
The number of services and containers is
configurable
18
Lightweight Service Container
A way to host and control services across
platforms
BusinessCommunications
Invocation and Management Framework
19
ESB endpoint is event-driven
Behavior controlled through configuration not code
Rejected Message
Entry
Exit
Entry
DirectoryCache
Fault
Tracking
Endpoints
Transformation Service
Tracking
20
Configurable Endpoints
Workflow Supported Exception Processing (WSEP)
ESB
1
1b
CustomService
21
Location transparency
Single namespace allows named addressing
Physical location of services is configurable
22
Multiple, Configurable Interaction Models
Interaction model between services is configurable
23
Service Orchestration
Assembling services into processes
24
Intermediary Services and Adapters
Provide routing, transformation and connectivity
3
2
3b
1
2b
?
1. Route2. Transform3. Process2b. Custom3b.
File Drop
?
?
?
?
25
Portal Integration
26
SOA and ESB Its all about the Architecture
Distributed Services Architecture
Maps of logical service interactions to physical
IT assets Transparent support for request-based
or event-driven service models
Logical model and physical deployment can be
changed without application recoding
27
SOA and ESB Its all about the Architecture
Business Process, Services, Network Topology
London
Chicago
Singapore
Svc1
Svc2
Svc3
Secure, Scalable, Message Broker Clustering,
Continuous Availability
28
?
Q A