successful business-critical soa: do's and...
TRANSCRIPT
Notes accompany this presentation. Please select Notes Page view.These materials can be reproduced only with written approval from Gartner.Such approvals must be requested via e-mail: [email protected] is a registered trademark of Gartner, Inc. or its affiliates.
Successful Business-Critical SOA:
Do's and Don'ts
Massimo Pezzini
Beware of SOA Bigotry:
“Request/Reply" SOA Is Not the IT Cure-all
Multichannel Operations
Web commerce
Internet banking
Travel reservations/ticketing
Self-Service Portals
Customers
Suppliers
Employees
Citizens (e-government)
Composite Applications
Contact center operations
Branch operations:
Banking
Post office
Single view of "something"
Real-Time B2B
Event-driven Applications
Securities trading
Telecom services activation
Real-time fraud detection
Real-time supply/demand chain
Airline operations tracking
Near-real-time data consistency
Batch-Oriented Processing
Bill/statement printing
Data warehouse loading
Database reconciliation
"Monitoring" Applications
Systems & Network Monitoring
Indoor positioning
Industrial processes
EDI-Style B2B
Suitable Applications for “Request/Reply" SOA
Applications Requiring SOA and Events
Key Issues
1. Why will organizations adopt SOA for strategic purposes?
2. What are the critical SOA adoption stages that users will typically go through?
3. What are the key technical and organizational obstacles to successful SOA, and how can enterprises overcome them?
A well executed SOA initiative will enable your
company reduce time-to market and achieve greater
business agility (…and will help you reduce IT costs as
well).
SOA Is a Mainstream Trend
0
10
20
30
40
50
60
70
80
Asia Europe North America Total
Currently using
Planning to implement withinthe next 12 months
Not currently using and noplans to use in the next 12months
Percentage of Respondents
SOA Adoption Breakdown by Geography
Source: Gartner (September 2008)
Why Service-Oriented Architecture?
Business Drivers Prevail Over IT Drivers
Call center integration
Single face to clients, suppliers, employees
Process integration
Real-time B2B
"Doing more with less"
Business/IT alignment
Data consistency/quality
Time to deployment
"Top Down" Enterprise Drivers
"Bottom Up" Business Unit Drivers
"Perennial" IT Challenges
SOA
M&A/divestitures
Multichannel sales/support
Time to market
Continuous innovation
Process flexibility
Process visibility
Skills is the Major Obstacle to SOA
Adoption
Why doesn't your organization currently use or plan to implement
SOA in the next 12 months?
60
50
48
44
40
40
23
13
6
0 10 20 30 40 50 60 70
Lack of internal SOA expertise
No perceived business value in SOA implementation
Lack of skill sets
Cost and/or resources required to implement SOA
Lack of organizational buy-in
SOA is a relatively new/ evolving concept, waiting
to see more industry/ peer-group justifications
SOA seen as too complex
Do not have the need
Don't know
Percentage of RespondentsSource: Gartner (September 2008)
Where Will Users Source Their
Business Services From?
TCO Differentiation
On-Demand Services (SaaS)
Purchased Services (Packaged Applications)
Custom Services (Built/Wrapped)
Composite Application/Mashup (Packaged/Custom)
Composite Process (Packaged/Custom)
Business Impact of Services
Stages of SOA Adoption
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
IT Goals Proof of Concept
Establish Technology
Platform
Leverage Services Sharing
Enterprise SOA Infrastructure
Business GoalsAddress
Specific Pain(That is, Customer
Portal)
Process Integration(That is, B2B)
Process Flexibility
(That is, Time to Market)
Continuous Adaptation &
Evolution
Single Application
MultipleApplications(Single BU)
MultipleApplications(Cross BUs)
Virtual Enterprise
Scope
<25 <100 <500 >500
<5 <25 <50 >50
<10,000 <100,000 <1,000,000 >1,000,000
<10 <20 <100 >100
No. of Published Services*
No. of Service Consumers*
No. of Service Calls/Day*
No. of Service Developers*
Enabling Technology
(cumulative)
Application Server, Portal,
Adapters
ESB, WSM Integr. Suite,
B2B
SOA Reg/Rep BPM Policy
Mgmt.
Enterprise SOA
backplane
* =These figures represent typical scenarios, but they may vary considerably
depending on the specific organization's requirements.
Which Stage of SOA Adoption
Are You Ready For?
Required Management
Buy-in
Required Skills
Required Organizational
Capabilities
= ImperativeO = Recommended
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
P P P P
O P P P
Head of IT Operations O P P
CIO/Business Units
O
P
CEO
O P
P
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
P P P P
O P P P
O P P
O
PO P
P
Basic Middleware P P P P
Web Services P P P P
Enterprise Service Bus P P P
Business Process Management Tools
P PDevelopment of Applications (SODA)
PO
O
O
P
SOA Operations Management
PO P
P P P P
P P P P
P P P
P P
PO
O
O
P
PO P
O P P P
Life Cycle Management O P P
Service DesignMethodology O P P
Planning Control and Quality Management P
PService Reuse Methodology
P
O
O
Domains
Cost Allocation Schema
EnterprisewideGovernance Processes
EnterprisewideSOA Backplane
P
PO
PO
PO
PO
Operation Management PO P
O P P P
O P P
O P P
P
P
P
O
O
P
PO
PO
PO
PO
PO P
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
P P P P
O P P P
O P P
O
PO P
P
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
X
X
XX
P P P P
P P P P
P P P
P P
PO
O
O
P
PO P
X
X
X
X
O P P P
O P P
O P P
P
P
P
O
O
P
PO
PO
PO
PO
PO P
X
X
X
X
X
X
X
X
X
X
SOA Center of Excellence
Service-Oriented
Head of Development or Head of Integration
CTO/Head of Architecture
Why SOA Initiatives Fail:
Technology or Governance?
Introduction Spreading Exploitation Plateau
Risk of SOA Project Failures
Lack of Governance
Risk
Technology Risk
Less Risk
More Risk
Time
The Seven Golden Rules
for the Perfect First SOA Project
1. Set Goals and Collect Business-IT Requirements
2. Segregation of Duties Application Design Teams:
• Service consumers
• Service implementations
Infrastructure Design Team (the future SOA CoE)
3. Joint Design/Independent Implementations Services jointly designed by application teams
Technically validated by the infrastructure team
4. Deliver Infrastructure (SOA backplane) First Design, implementation, testing
Validation against an agreed proof-of-concept
5. Deliver Services Before Consumer Applications Plan for services to be available and tested before relevant consumers
6. Test, Test and Test Again Plan for at least 25% of development effort on integration testing
7. Log, Log and Log Again Multiple turn-on/off logs
Introduction
Service-Oriented Architecture Entails Tackling
Multiple Technology Challenges
Non-SOA Wrapped Application
Multichannel Portal
Composite Application (Mashup)
WrapperWrapper
Services Application Logic
Native SOA Application
Interface Interface Interface
SOA backplane
BPM Application
Wrapper
BPM Technology
Portal Product, EAS, Composite Application Tools,
Mash up tools
Portal Product
Adapters, Programmatic
Integration Servers
TPM, EAS
"All-in-One" Application Platform Suite
ESB, MOM, Appliances
Introduction
The SOA Backplane Must Support Both
Request/Reply and Event-Based SOA
Security Management Adapters
Development Tools
Life Cycle Management Tools
Orchestration Policies
ExtensibilityFramework
Communication
Mediation/Transformation
Routing/Addressing Naming QOS
Registry
SOA Backplane
ESB
ESB core:•Web services support•Discovery, binding, virtualization
•Reliable messaging•Publish-and-subscribe•Rule-based routing•Security, administration •Extensibility
ESB extensions:•Message validation •Message transformation•Content-based routing•Microflow, composition•Protocol bridging•Adapters•Logging, auditing, monitoring
•Failover, load balancing
Features specifically required for event-processing
Spreading
(SOAP, IIOP, JMS, MOM, RPC, ORB, TPM)
Flow Management in SOA:
One Size Doesn't Fit All
MicroflowsService
Composition Workflow
Key Features Subsecond execution
cycle Transaction support Usually nondistributed,
single platform State is not persisted
GoalImplement coarse-grained services by executing flows
among fine-grained services
GoalImplement services by executing flows among software components
Key Features Subsecond to minutes
execution cycle Compensation flows
(automated or manual) Distributed/multiplatform State may or may not be
not persisted
Key Features Minutes to months
execution cycle Compensation flows
(automated or manual) Distributed/multiplatform State must be persisted
GoalAutomate business processes involving
human tasks and services
Straight-Through Process
Key Features Minutes to hours
execution cycle Compensation flows
(automated or manual) Distributed/multiplatform State must be persisted
GoalAutomate business processes involving
multiple services
Spreading
ScopeSingle application
ScopeUsually single domain
ScopeSingle/multiple domains
ScopeSingle/multiple domains
Flow Management Enables SOA SOA Enables Process Integration
"Orchestration"
?
Standardized Business Objects Enable
Interoperability and Reuse
SAP ERP
Oracle Siebel CRM
Customer Data (SAP Format)
Customer Data (Siebel Format)
B2C E-Commerce Application
Customer Data (Custom Format)
Branch Office Packaged Application
Customer Data (ISV Format)
Customer Data (Standardized Format)
Spreading
Composite "Get Customer Data"
ServiceInterface
How Do You Know If You Are Doing It
Right or Wrong?
• Number of New Services Developed per Each New Consumer Application
• Time to Deployment for New Consumer Applications
• Cost of Application Maintenance
Cost Reduction
• # of Services Deployed
• # of Consumer Applications Deployed
• # of Services/# of Consumers
• # of Services Shared by at Least Two Applications
• Average Sharing Ratio
Optimal TrendExamples of SOA Technical Metrics
Reuse
Goal/Focus
• Volume of Service Requests
• Amount of Requests per Service
• Service Request Response Time
QOS
Spreading
SOA backplane
Greater Process Insight Is an Often
Unexpected Benefit of SOA
BAM
Business KPIs
Service Registry
SOA Metrics/KPIs
Business Events "Probe"SOA Events "Probe"
Exploitation
How Do You Enforce Sharing
of Services?
Service Definition Process
Service Registry and Life Cycle Management Tools
Incentives
Mainstream
Shareable Services "Chasing" Team
Aggressive
Standardized Business Objects
Exploitation
(a.k.a.: "Stick-and-Carrot")
Enterprisewide SOA Is Multiowned
and Federated
Domestic Sales
Administration
Production
Int'l Sales
Customer Support
CustomersSuppliersContractorsOutsourcers
Enterprise SOA
SOA Federation
SOA Domains
Plateau
Reaal Verzekeringen — Competitive Advantage in
Insurance Through Federated SOA
Multidomain Service Registry/Repository
Business domains
Service usage statistics
Distributie-
management servicesVolmacht services
Betalingsverkeer
services
Document-
management services
Productmanagement
services
Relatiemanagement
services
Leven services
Hypotheek services
Actuariële, Financieel
Management en
Management
Informatie services
Collectief pensioen
services
Schade services
Herverzekering
services
Individueel pensioen
services
Leveranciers-
management services
IT ontwikkel en
beheer services
Co-assurantie
servicesBancaire services
Productspecifieke
servicedomeinen
IT-specifieke
servicedomeinen
Servicedomeinen voor
bedrijfsondersteunende
services
Legenda
AOV services
Utility services
Workflowservices Rekenservices Vertaalservices
Servicedomeinen voor
alle productdefinities en
relaties
Service metadata
SOA hasn't been ordered by the doctor: you can live without it.
However, most organizations will be forced to SOA by packaged
application vendors.
Enterprisewide SOA is a long journey
Most of the times it is best traveled in multiyear incremental implementation steps
SOA success is a 50-50 business between technology and governance.
SOA doesn't happen by magic.
A sound combination of "stick" and "carrot" is often needed to
achieve alignment with SOA goals and principles.
SOA “extremism” may be your worst enemy
Conclusions
Business Imperative Action Plan
• Monday Morning
- Non SOA literates: Look for opportunities for SOA to support business needs with short-medium term paybacks.
- SOA Literates: Establish an initial set of “light” (but formal) SOA governance processes.
• The Next 12 Months
- Look for opportunities to expand the footprint of your SOA initiative to support cross-functional business requirements aimed at business agility.
- Introduce BAM or other simpler forms of event processing to collect greater, real-time business insights.
• On the Radar Screen
- Analyze whether SOA can support business transformation initiatives (e.g., Multi-enterprise B2B Integration, Real-time Enterprise)
- Asses the potential business benefits (for your organization) of Event-processing & Federated SOA.