soa 101
TRANSCRIPT
SOA 101
David S. Linthicum
• Blogs:– eBizq.net “Linthicum Channel”– IT Toolbox “CEO’s Guide to SOA and Application
Integration”– InfoWorld “Real World SOA”
• Weekly Podcast– www.soaexpertpodcast.com
• New Gig– CEO BRIDGEWERX
• New Book: 12 Steps to SOA
SOA…What’s New Here?
The Integration Challenge…
The N-squared Integration Problem:
Source: Copyright © 2002 ZapThink, LLC
ContentManagement
Web Site
File System
RDBMS
Office Documents
B2B Exchanges
Directory
ERP / CRMSystems
Mainframe / Legacy
NetworkedDevices
No
N- o
r S
EM
I-S
TR
UC
TU
RE
DS
TR
UC
TU
RE
D
…Made Worse by External Integration
• 70% of IT development budgets are spent on integrating different systems – ZapThink
Source: Copyright © 2002 ZapThink, LLC
ContentManagement
Web Site
File System
RDBMS
Office Documents
B2B Exchanges
Directory
ERP / CRMSystems
Mainframe / Legacy
NetworkedDevices
No
N- o
r S
EM
I-S
TR
UC
TU
RE
D
STR
UC
TU
RE
D
Source: Copyright © 2002 ZapThink, LLC
ContentManagement
Web Site
File System
RDBMS
Office Documents
B2B Exchanges
Directory
ERP / CRMSystems
Mainframe / Legacy
NetworkedDevices
No
N- o
r S
EM
I-S
TR
UC
TU
RE
D
STR
UC
TU
RE
D
The “Rat’s Nest” Architecture
FBT PAY GNTS
TRDS
Client
Customs
RREIPS Integrated A/C Refunds
RBADef
PaymentsExcise
CR
PKI
ECI ADD AWA ELS
Client Staff RemoteStaff
TAXAGENTS
GCI
Call Centers
WOC
CCD
TASS
StaffPhone
ComplianceStaff
BOA
Ref material
Bus. Intel
NTS A/c
BEP
CDCCCWMS
BANK
DDDR
1
Data…….
Penalty
Business
IVR
1
IT: Fulfilling Business Requirements
Business Requirements• Service Customers• Manage Operations• Increase Worker Productivity• Communicate with market• Ensure reliable and secure
operations• Develop new products and
services• Respond to new business
drivers
IT Capabilities• Implement CRM Systems• Implement ERP Systems• Manage desktop environments• Manage server environments• Manage email systems and web
sites• Manage network and storage
operations• Develop applications
However, it rarely works that way…
?Final Im
plementation
Long development
cycleIT
Interpretation
Business Requirements
• Requirements change
• Interpretations often inaccurate or limited
• Lengthy development cycles impervious to change
• Implementations “cast in concrete”
Result: IT that places Result: IT that places limitations on Businesslimitations on Business
What is a Service-Oriented Architecture?
• Access software via Services that are easy to find and connect to
• Web Services provide a standard way of building and accessing Services
• Developers & integrators can build applications out of Services
Application Integration Solution Types
The High Level Integration Stack
Logic
Transformation Formatting
Data
Logic
User Interface
Data
Service Oriented Application Integration
• Service integration to create a composite application
• Sharing business logic
• Sharing code
• Sharing processing– Shared programs– Shared transactions– Shared objects
Application Integration is Evolving
Business Process Control (Process Integration Oriented)
Contrasting Three Forms of Integration
Data Consistency Multi-step Process Service Oriented Loosely coupled integration Multiple applications Asynchronous dominates One-way Simple abstraction of
business rules
Loosely coupled integration Multiple applications Can be either
Asynchronous or Synchronous based
One-way and request/reply Limited complexity in
abstraction of business rules
Loosely or tightly coupled integration
Single application Synchronous dominates Request/reply Complex abstraction of
business rules
Multistep Process (Information-Oriented) Dominates… For Now
Process Orchestration will Control SOA
Composite Application
Value of Services
• Limitations of information-oriented integration– Limited visibility– Limited reuse– Latency
• Advantages of leveraging service-oriented integration– Visibility at the information and the behavior levels– Reuse of services among trading partners– Real-time integration
The Economics of Integration
Initial Costs Customization ChangesMaintenance
Custom Integration
Copyright (C) 2002 ZapThink, LLC
Rel
ativ
e C
osts
The Relative Costs of Different Integration Approaches
The Economics of Integration
Initial Costs Customization ChangesMaintenance
Custom Integration
Copyright (C) 2002 ZapThink, LLC
Rel
ativ
e C
osts
The Relative Costs of Different Integration Approaches
Traditional EAI, B2Bi
The Economics of Integration
Initial Costs Customization ChangesMaintenance
Custom Integration
Copyright (C) 2002 ZapThink, LLC
Rel
ativ
e C
osts
The Relative Costs of Different Integration Approaches
Traditional EAI, B2BiWeb Services "Adapters"
The Economics of Integration
Initial Costs Customization ChangesMaintenance
Custom Integration
Copyright (C) 2002 ZapThink, LLC
Rel
ativ
e C
osts
The Relative Costs of Different Integration Approaches
Traditional EAI, B2BiWeb Services "Adapters"Service-Oriented Integration
The Economics of Integration
Initial Costs Customization ChangesMaintenance
Custom Integration
Copyright (C) 2002 ZapThink, LLC
Rel
ativ
e C
osts
The Relative Costs of Different Integration Approaches
Traditional EAI, B2BiWeb Services "Adapters"Service-Oriented Integration
Development model for SOA
•Integration tightly couples end-points•Interoperability considers each end point separately
– Producer: Provides service
– Consumer: Consumes the service
•Producer/Consumers describe their interfaces and are then connected at run time (late binding)
•Focus on agreement of business service interface– Do not focus on operating system, implementation, etc….
Producer ConsumerSOA
(SharedServices)
Consumer
Interface
Producer
Interface
Application Domain Integration
Domain
Data Domain Point of Access
Domain
Business ArchitectureBusiness ArchitectureBusiness Architecture
Patterns
Business Relationship Grid
Bricks
Business Processes, Styles
System Management Domain
Security Domain
Infrastructure Domain
InformationArchitecture
Technical Architecture
Gartner’s Architecture
Directions for SOA
Three Levels of Web Service Engagement
Goals and Characteristics of a SOA
• Improved Adaptability and Agility– Respond to business needs in near real-time
• Functional Reusability– Eliminate the need for large scale rip and replace
• Independent Change Management– Focus on configuration rather than programming
• Interoperability instead of point-to-point integration– Loosely-coupled framework, services in network
• Orchestrate rather than integrate– Configuration rather than development to deliver business needs
Business Benefits of Loosely Coupled Approach
Thanks!