Transcript ConferenceCode_SessionCode

Beyond the Hype: SOA Adoption and
Technology Landscape
Massimo Pezzini
Notes accompany this presentation. Please select Notes Page view.
These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected].
How Do You Know SOA When You See It?
 Modular software
 Client-decoupled server modules
 External access to modules
(services)
 Loose coupling (black box)
Enterprise Service
Service
Consumer Service Bus Implementation
(ESB)
(Client)
 Designed to be useful and usable by
other applications
 Useful and usable by other
enterprises
 Centrally-managed repository and
registry for interfaces, rules and
policies
 Centrally-managed run-time
middleware network for service
interactions
Interface
Proxy
Interface
Registry
Repository
(Metadatabase)
Irresistible Forces Push SOA
Into Mainstream Adoption
Enablers:
ESB
Complex Event Processing
SOA-Based Packaged Applications
SOA
Adoption
Enablers:
Integration Middleware
Enablers:
Web Services
MOM
J2EE, .NET
CORBA, DCOM,
BPM
Screen-Scrapers
Enablers:
Peer-to-Peer Networks
RPC, Distributed TPMs
Stored Procedures
1995
Drivers:
Business Flexibility
Interenterprise BPM
"Everybody is doing it"
Drivers:
B2B "Lite"
Multichannel Composite Applications
"Doing more with less"
Drivers:
Mergers & Acquisitions
E-business
2002
2008
Time
Why Service-Oriented Architecture?
Business Drivers Prevail Over IT Drivers






M&A/divestitures
Multichannel sales/support
Time to market
Continuous innovation
Process flexibility
Process visibility
"Top Down" Enterprise Drivers
"Perennial" IT Challenges


SOA






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
"Bottom Up" Business Unit Drivers
Beyond the SOA Hype: What's for Real?
Benefits
Architectural Partitioning
 Diverse life-cycle "speeds"
 Synergy of different technologies
 Optimal tech skills allocation
 Processes visibility
 Greater maintainability
 Easier outsourcing/"offshoring"
Incremental Deployment
 Gradual migration
 Cost "spreading" across projects
 Reduced maintenance cost
Sharing (Reuse) of Services:
 Faster time to deployment
 Lower development cost
 Greater adaptability
Implications
Higher Upfront Costs
 Cultural change
 Infrastructure (SOA backplane)
 More formal methodology
 Longer design time for services
 Testing (unit/end-to-end)
More Distributed Infrastructure
 Extensive use of middleware
 Transaction management
 Debugging/troubleshooting
 End-to-end management
 More granular security
 Metering/logging
Tighter Management/Governance
 Ownership/accountability
 Cost allocation
 Prioritization/conflict resolution
SOAP and WSDL Are Not Enough: Orient
Yourself Through the Middleware Bazaar
Spreading
E-APS
Native SOA Application
Non-SOA Wrapped Application
Services
Application Logic
Wrapper
Interface
TPM, EAS
Wrapper
Interface
Wrapper
Interface
SOA Backplane
(Subset of the Enterprise Nervous System)
ESB, MOM, ORB,
TPM, IBS, Appliances
BPM
Application
Portal Product, Multichannel
SES
Portal
Composite
Application
Adapters, Programmatic
Integration Servers
BPM Suite, IBS
Portal Product, EAS,
Presentation Integration Server
The SOA Backplane Unveiled:
Web Services and More
Life-Cycle Management
Tools
Development
Tools
Orchestration Registry Policies Security Management Adapters
Extensibility
Framework
Routing/
Addressing
Naming
QOS
Mediation/
Transformation
Communication
(SOAP, IIOP, JMS, MOM, RPC, ORB, TPM)
= Minimal Features
= Common Features
= Advanced Features
An ESB Is a Message Bus
for SOA Applications
 Service discovery, binding, multiprotocol communication
 Web services (URL, XML, SOAP, WSDL, HTTP)
 Runtime support of service deployment and policies (SCA, WCF)

Reliable message delivery
Browser
UserFacing
Logic

Rich
Client
Load balance, failover

Security

Publish and Subscribe
BPM
ESB
Organizational Maturity: Software Coordination
Begins with People Coordination
Technology of IT
Organization of IT
Platform
for SOA
Applications
Enterprise Nervous
System (ENS)
Platform
for SOA
Governance
SOA Center of Excellence
Middleware Technology Hype Cycle
visibility
Enterprise Service Bus
Managed File Transfer
Packaged Integration
Business Activity Monitoring
Web Services Management
Service Registry
Integration Repositories
B2B Gateway Software
XML Appliances
Extensible Microkernel-Style Platforms
Event-Driven Architecture
Alternative Open-Source
Application Platforms
Business Process Networks
Distributed
Caching
Platforms
Integration Competency Centers
Advanced Web Services
Vocabulary-Based
Transformation
Event-Based
Application
Platforms
Presentation
Integration Servers
J2EE
Programmatic Integration Servers
Basic Web Services
Integration Service Providers
Microsoft .NET Application Platform
Integration Suites
Open-Source J2EE
Enterprise-Scope Application Platform Suites
SOA
Grid-Based Application Platforms
Service Component Architecture
As of July 2006
Technology
Trigger
Peak of
Inflated
Expectations
Trough of
Disillusionment
Slope of Enlightenment
Plateau of
Productivity
time
Years to mainstream adoption:
less than 2 years
2 to 5 years
5 to 10 years
more than 10 years
obsolete
before plateau
Recommendations
 SOA is not a passing fad. It is here to stay for
the long run.
 ESB, Repository/Registry, WebServices
Management and BPM are the key technology
enablers.
 Processes, governance and the SOA Center of
Excellence are the key organizational enablers
 ... But SOA is not finished. It will evolve into and
Advanced SOA absobing additional approches
and technologies.