Beyond the Hype: SOA Adoption and Technology Landscape

1
Beyond the Hype SOA Adoption and Technology
Landscape

• Massimo Pezzini

2
How Do You Know SOA When You See It?

• 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 Implemen-tation
Service Consumer (Client)
Enterprise Service Bus (ESB)
Interface
Interface Proxy
Registry Repository (Meta-database)
3
Irresistible Forces Push SOAInto Mainstream
Adoption
SOA Adoption
Enablers Peer-to-Peer Networks RPC, Distributed
TPMs Stored Procedures
Time
2002
1995
2008
4
Why Service-Oriented Architecture? Business
Drivers Prevail Over IT Drivers

• MA/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
5
Beyond the SOA Hype What's for Real?
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

6
SOAP and WSDL Are Not Enough Orient Yourself
Through the Middleware Bazaar
Spreading
E-APS
Non-SOA Wrapped Application
Native SOA Application

Services
Application Logic
Wrapper
Wrapper
Wrapper
Interface
Interface
Interface
TPM, EAS
SOA Backplane (Subset of the Enterprise Nervous
System)
Adapters, Programmatic Integration Servers
ESB, MOM, ORB, TPM, IBS, Appliances
BPM Application
BPM Suite, IBS
Composite Application
Portal Product, SES
Multichannel Portal
Portal Product, EAS, Presentation Integration
Server
7
The SOA Backplane UnveiledWeb Services and More
Development Tools
Life-Cycle Management Tools
Registry
Security
Management
Adapters
Orchestration
Policies
Mediation/ Transformation
Routing/ Addressing
Extensibility Framework
Naming
QOS
Communication (SOAP, IIOP, JMS, MOM, RPC, ORB,
TPM)
Common Features
Advanced Features
Minimal Features
8
An ESB Is a Message Busfor 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

ESB
9
Organizational Maturity Software Coordination
Begins with People Coordination
Technology of IT
Enterprise Nervous System (ENS)
10
Middleware Technology Hype Cycle
11
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.