0. Beyond the Hype: SOA Adoption and Technology Landscape
Application Integration: Now That It's Mainstream, What's Next?
Beyond the Hype: SOA Adoption and Technology Landscape
Massimo Pezzini
8-13 October
Orlando, FL
Symposium/ITxpo 2006 Roy Schulte
October 8-13, 2006
Walt Disney World Dolphin
Orlando, FL
These materials can be reproduced only with Gartner's written approval. Such approvals must be requested via —

1. How Do You Know SOA When You See It?
Key Issue: What is SOA and how does it differ from other software architectures?
Tactical Guideline: Service interface is fundamental to design of a service in SOA. Service registry is fundamental to basic functioning of a service-oriented application.
Modular software
Client-decoupled server modules
External access to modules (services)
Loose coupling (black box)
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
Service Consumer (Client)
Enterprise Service Bus (ESB)
Service Implemen-tation
Interface Proxy
Interface
Registry
Repository (Meta-database)

2. Irresistible Forces Push SOA Into Mainstream Adoption
Strategic Planning Assumption: By 2010, at least 65 percent of large organizations will have more than 35 percent of their application portfolios SOA-based, up from fewer than 5 percent of organizations in 2005 (0.8 probability).
Enablers:
ESB
Complex Event Processing
SOA-Based Packaged Applications
Drivers:
Business Flexibility
Interenterprise BPM
"Everybody is doing it"
Drivers:
B2B "Lite"
Multichannel Composite Applications
"Doing more with less"
Enablers:
Integration Middleware
Web Services
J2EE, .NET
BPM
SOA
Adoption
Drivers:
Mergers & Acquisitions E-business
Enablers:
MOM
CORBA, DCOM,
Screen-Scrapers
Enablers:
Peer-to-Peer Networks
RPC, Distributed TPMs
Stored Procedures
Time
1995
2002
2008

3. Why Service-Oriented Architecture
Why Service-Oriented Architecture? Business Drivers Prevail Over IT Drivers
Key Issue: Which key factors must enterprises consider when deciding whether to move to SOA or not?
Strategic Planning Assumption: Through 2008, fewer than 30 percent of strategic SOA initiatives will be justified solely in terms of IT benefits (0.9 probability).
M&A/divestitures
Multichannel sales/support
Time to market
Continuous innovation
Process flexibility
Process visibility
"Top Down" Enterprise Drivers
"Perennial" IT Challenges
"Doing more with less"
Business/IT alignment
Data consistency/quality
Time to deployment
SOA
Call center integration
Single face to clients, suppliers, employees
Process integration
Real-time B2B
"Bottom Up" Business Unit Drivers

4. Beyond the SOA Hype: What's for Real?
Strategic Planning Assumption: Through 2008, the upfront investment for large-scale service-oriented applications will be justifiable only for projects with a planned lifetime of three years or more (0.8 probability).
Benefits
Implications
Architectural Partitioning
Diverse life-cycle "speeds"
Synergy of different technologies
Optimal tech skills allocation
Processes visibility
Greater maintainability
Easier outsourcing/"offshoring"
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
Incremental Deployment
Gradual migration
Cost "spreading" across projects
Reduced maintenance cost
Sharing (Reuse) of Services:
Faster time to deployment
Lower development cost
Greater adaptability
Tighter Management/Governance
Ownership/accountability
Cost allocation
Prioritization/conflict resolution

5. (Subset of the Enterprise Nervous System)
SOAP and WSDL Are Not Enough: Orient Yourself Through the Middleware Bazaar
Tactical Guideline: Point-to-point Web services connections can be used only for small-scale, experimental service-oriented application projects. A middleware-based intermediary — the SOA backplane, which implements an integration fabric — is required if the number of services deployed grows beyond 25 to 30.
Spreading
E-APS
Native SOA Application
Non-SOA Wrapped Application
Services
Application Logic
Wrapper
Wrapper
Wrapper
TPM, EAS
Interface
Interface
Interface
SOA Backplane
(Subset of the Enterprise Nervous System)
Adapters, Programmatic Integration Servers
ESB, MOM, ORB, TPM, IBS, Appliances
BPM
Application
BPM Suite, IBS
Portal Product, SES
Composite
Application
Multichannel
Portal
Portal Product, EAS, Presentation Integration Server

6. The SOA Backplane Unveiled: Web Services and More
Strategic Planning Assumption: Until 2009, implementation of a sound SOA backplane will remain the single most important technical obstacle in SOA projects (0.9 probability).
Life-Cycle Management
Tools
Development
Tools
Orchestration
Registry
Policies
Security
Management
Adapters
Extensibility
Framework
Routing/
Addressing
Mediation/
Transformation
Naming
QOS
Communication
(SOAP, IIOP, JMS, MOM, RPC, ORB, TPM)
= Minimal Features
= Common Features
= Advanced Features

7. An ESB Is a Message Bus for SOA Applications
Strategic Imperative: Point-to-point connectivity is not enough. Companies that deploy large-scale or long-lived SOA applications must use some type of middleware infrastructure, such as an ESB, to mediate the interactions among service components.
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
User-
Facing
Logic
Load balance, failover
Rich
Client
Security
Publish and Subscribe
BPM
ESB

8. SOA Center of Excellence
Organizational Maturity: Software Coordination Begins with People Coordination
Strategic Planning Assumption: By 2010, more than 60 percent of SOA projects will actively involve a central integration competency center (0.8 probability).
Technology of IT
SOA Center of Excellence
Organization of IT
Platform for SOA Applications
Platform for SOA Governance
Enterprise Nervous System (ENS)

9. Middleware Technology Hype Cycle
Market: The software infrastructure that provides the foundation for modern business applications is undergoing a transformation that directly affects architects, application developers and middleware technologists, and indirectly affects all layers of IT management and line-of-business management
Technology Trigger
Peak of
Inflated Expectations
Trough of Disillusionment
Slope of Enlightenment
Plateau of Productivity
time
visibility
Years to mainstream adoption:
less than 2 years
2 to 5 years
5 to 10 years
more than 10 years
obsolete
before plateau
As of July 2006
J2EE
Presentation Integration Servers
Integration Competency Centers
Programmatic Integration Servers
Basic Web Services
Integration Service Providers
Microsoft .NET Application Platform
Integration Suites
Open-Source J2EE
Enterprise-Scope Application Platform Suites
SOA
Advanced Web Services
XML Appliances
B2B Gateway Software
Managed File Transfer
Enterprise Service Bus
Web Services Management
Packaged Integration
Business Activity Monitoring
Service Registry
Integration Repositories
Extensible Microkernel-Style Platforms
Event-Driven Architecture
Distributed Caching Platforms
Business Process Networks
Vocabulary-Based Transformation
Grid-Based Application Platforms
Event-Based Application Platforms
Service Component Architecture
Alternative Open-Source Application Platforms

10. 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.