Overview of Service-Oriented...
Transcript of Overview of Service-Oriented...
1
Copyright © 2006, ZapThink, LLC 1
Overview of Service-Oriented Architecture
Jason BloombergZapThink, LLC
Take Credit Code: HGOVER
Copyright © 2006, ZapThink, LLC 2
Business Constant: Change
CHANGE
CompetitionCompetition
Changing Changing MarketplaceMarketplace Customer Customer
DemandsDemands
Mergers & Mergers & AcquisitionsAcquisitions
Optimizing Optimizing ProcessesProcesses
New New TechnologiesTechnologies
Business Business PartnersPartners
A Business is Never A Business is Never STATICSTATIC
2
Copyright © 2006, ZapThink, LLC 3
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
Copyright © 2006, ZapThink, LLC 4
However, it rarely works that way…
?
Final Implementation
Long development
cycle
IT
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
3
Copyright © 2006, ZapThink, LLC 5
We’ve had IT challenges for years …
Copyright © 2006, ZapThink, LLC 6
… but even after yesterday’s promises…
4
Copyright © 2006, ZapThink, LLC 7
… we still have the same IT mess, only worse.
Copyright © 2006, ZapThink, LLC 8
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
5
Copyright © 2006, ZapThink, LLC 9
…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
ST
RU
CT
UR
ED
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
ST
RU
CT
UR
ED
Copyright © 2006, ZapThink, LLC 10
What have you seen?
• Have you seen any issues similar to those just pointed out in your organization?
• The discrepancy between IT capabilities and business needs?
• IT challenges, new promises that turned out to create new problems?
• Integration challenges exacerbated by external B2B integration requirements?
6
Copyright © 2006, ZapThink, LLC 11
Integration Approaches of Yesterday
• Custom Integration: Coding to Interfaces
– APIs: COM, Java, COBOL, Assembly?– Distributed Computing?: DCOM, CORBA– Screen-Scraping and Emulation (3270 and
HTML)– Message-Queues
• EAI and B2Bi Middleware
– Automating interface-level integration– Bus or hub-and-spoke architecture
Fundamentally Fundamentally brittlebrittle approaches to approaches to integrationintegration
Copyright © 2006, ZapThink, LLC 12
There’s Got to Be a Better Way!
Rather than trying to simply throw more software and Rather than trying to simply throw more software and iron at the problem, we need a better way of organizing iron at the problem, we need a better way of organizing our IT resourcesour IT resources
• Service-Oriented Architecture (SOA) represents a fundamental evolution in the IT industry
– The core business motivation is business agility.– Rather than “rip and replace” old systems – make them
work better together– We don’t want more middleware for our middleware– As fundamental a change as mainframe to client/server or
client/server to the Internet
7
Copyright © 2006, ZapThink, LLC 13
SOA: Definition
An approach to building and managing distributed computing infrastructures that considers IT resources as Services available and discoverable on a network.
Copyright © 2006, ZapThink, LLC 14
SOA Features
• SOA is architecture – a set of best practices for the organization and use of IT
• Abstracts software functionality as loosely-coupled, business-oriented Services
• Services can be composed into business processes (which are also Services) in a declarative manner
8
Copyright © 2006, ZapThink, LLC 15
SOA: Implication
Rather than dealing with isolated systems that must be integrated after the fact, Service Orientation provides business users with understandable Services they can call upon and compose into business processes as needed – building systems that can adapt as the business changes.
Copyright © 2006, ZapThink, LLC 16
SOA: Benefit
The Service Orientation vision is therefore one of providing the business values of agility and flexibility for users of technology, coupled with an abstraction layer that simplifies the complexity of today’s heterogeneous IT environments from those users.
9
Copyright © 2006, ZapThink, LLC 17
Characteristics of SOA
• Services are loosely coupled – making a change to a service provider does not mandate changing any service consumers.
• Business processes are composed of services, and are in turn exposed as services.
• Services are policy-driven – business users can change how a service behaves.
• Systems are inherently integrated by virtue of composable services – not through layers of middleware.
Copyright © 2006, ZapThink, LLC 18
Characteristics of SOA(Cont.)
• Services leverage legacy systems – SOA does not mandate replacement of runtime infrastructure.
• In SOA, metadata controls how the system behaves instead of code – business logic trumps application logic.
• In SOA, it’s the contracted interface that matters, not the underlying runtime environment.
10
Copyright © 2006, ZapThink, LLC 19
SOA is Enterprise Architecture
What is Architecture?The fundamental organization of a system embodied by its
components, their relationships to each other and to the environment and the principles guiding its design and evolution. (IEEE P1471/D5.3)
Enterprise architecture includes:• An aggregated architecture of all the individual IT systems
within an organization • The human element within the enterprise• Systems, people, and organizational constructs at other
companies that have relationships with the enterprise• Individual consumers who are that enterprise’s customers• Corporate governance
Copyright © 2006, ZapThink, LLC 20
SOA is a discipline…
• Implementing a Service-Oriented Architecture is a journeyjourney
• Moving from proprietary interfaces to standards-based ones is just the first step…
• SOAs require a combination of security, management, governance, integration, process, and architecture tools
• What are the right steps to guarantee overall success?
• How can you guarantee an ROI while reducing risk?
11
Copyright © 2006, ZapThink, LLC 21
Don’t Get Lost in the Terminology
• There are many styles for SOA implementation
• Focus on your goals: Reuse? Governance? Reduced integration cost? Agility?
ESB? EAI?
SOA?EDA?EDA?
Fabric?
Abstraction?SOA Infrastructure?
Service Grid?Service Network?
Copyright © 2006, ZapThink, LLC 22
SOA’s Little Secret
• You can build SOA with whatever software you already have (for the most part)
• When considering purchasing software for your SOA initiative, look to fill the functionality gaps in your current portfolio
• Don’t just add middleware for your middleware!
12
Copyright © 2006, ZapThink, LLC 23
CompositeApplication
Delivery
BusinessServices
BusinessProcesses
SOA Fabric AtomicServices
Data Integration
Legacy Applications
and Middleware
SOA: A Technology View
Databases
Governance and Security InfrastructureGovernance and Security Infrastructure
SecuritySecurity
ManagementManagement
RoutingRouting
TransformTransform
AA
BBCC
DD
EE
AA
BBCC
DD
EE
MessagingMessaging
Rich Rich ClientsClients
Composite Composite AppsApps
DiscoveryDiscovery
Source: MW2 Consulting
Copyright © 2006, ZapThink, LLC 24
Have We Been Here Before?
• Service-Oriented Architectures have been around a while
• CORBA (Common Object Request
Broker Architecture) and DCOM (Microsoft Distributed Component Object
Model) two familiar examples• What’s new this time?
13
Copyright © 2006, ZapThink, LLC 25
The Difference is Web Services
Web Services Coordination
WS-SecureConversation
WS-BusinessActivity
Web Services Metadata Exchange
Web Services for Remote Portlets
WS-Transfer
WS-CoordinationWS-Trust
BPEL and BPELJ
Web Services Business Activity Framework
Web Services Dynamic Discovery
Web Services Transaction
WS-AtomicTransaction
Web Services Eventing
WSDL
WS-Federation
WS-Acknowledgement
WS-ReliableMessaging
WS-Addressing
WS-Policy
WS-MessageData
WS-CallBack
WS-Choreography Interface
SOAP
UDDI
Copyright © 2006, ZapThink, LLC 26
Web Services = SOA?
• SOAP wrappers / Web Services adapters
• Replace proprietary APIs with standards-based APIs
• Still fine grained, may still be tightly coupled
• n-Tier architecture with addition of Web Services interface
• Less secure and more verbose
Problem: Same cake with new frosting
14
Copyright © 2006, ZapThink, LLC 27
SOA vs. Web Services
MainframeLogic
MainframeLogic
EISEIS CustomApp
CustomApp
Web Services Web Services Web Services
Security Security Security
Messaging Messaging Messaging
TransactionsTransactions
MainframeLogic
MainframeLogic
EISEIS CustomApp
CustomApp
Web Services Web ServicesWeb Services
SOA Abstraction LayerSOA Abstraction LayerTransactions Messaging Security
Business Services Data Services Discovery
Man
agem
ent
Mon
itorin
g
Standard architecture with Web Services
SOA leveraging Web Services
Source: HP
Copyright © 2006, ZapThink, LLC 28
Web Services are the Trees….
Service Orientation is the Forest
15
Copyright © 2006, ZapThink, LLC 29
Service orientation…the next big thing?
Approach TimeframeProgramming
ModelBusiness
Motivations
Mainframe timesharing1960s –1980s
Procedural (COBOL) Automated business
Client/server 1980s-1990s
Database (SQL) and fat client (PowerBuilder, Visual Basic)
Computing power on the desktop
n-Tier/Web 1990s-2000sObject-oriented (Java, COM)
Internet/eBusiness
Service orientation 2000sService-oriented (SOAP, WSDL, UDDI)
Business agility
Copyright © 2006, ZapThink, LLC 30
The Business Benefits
• IT resources are available as needed to businesses as Services
• Business users empowered to create and manage business logic
• The Service-oriented abstraction layer enables companies to run their operations and conduct business with each other in a dynamic and automated fashion
• Business drives IT, and agile IT enables agile businesses
16
Copyright © 2006, ZapThink, LLC 31
• What companies require is Business Agility…
»Responding quickly to change, and
»Leveraging change for competitive advantage
J
Business Agility
Copyright © 2006, ZapThink, LLC 32
SOA Hotspots
• Four key areas of SOA investment– Reduction in integration expense– Increase in Service / asset reuse– Increase in business agility– Enablement of governance &
compliance
• Key Problem areas– EAI replacement– Legacy enablement/migration– Shared Service development– Governance– Embedding processes in the
extended enterprise
17
Copyright © 2006, ZapThink, LLC 33
Thank You!
Photos © Lisa Polucci