SOA Scenario: Patterns and Guidelines for Starting With SOA and Moving to Advanced SOA

Anthony Bradley

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: vendor.relations@gartner.com. Gartner is a registered trademark of Gartner, Inc. or its affiliates.

SOA Proven Transformative Power

According to Gartner Research and 2008 SOA survey: Mainstream companies are gaining SOA value
Business agility benefits in over 60% of respondents Over 50% experienced dev productivity benefits Over 40% gained sharing benefits

SOA Emerging From Trough of Disillusionment

Some SOA success doesnt mean all SOA success

Still a large number of SOA disappointments Not SOA bad but bad SOA

Leaders and architects must understand SOA benefits and how to get there

From "Hype Cycle for Application Architecture, 2008 3 July 2008 (G00159029)

Key Issues 1. What is SOA and how can it deliver value? 2. What are and will be the prevailing software patterns in SOA? 3. How does IT modernization contribute to SOA? 4. What are the emerging software development practices and their affinity with SOA?

SOA Fundamentals
SOA is an architectural approach to building systems delivering 2 major categories of value
Gartners Five Criteria for a SOA Application

- Sharing (also called leverage and reuse) - Agility (ability to change more rapidly)
through 2 fundamental principles

1. Modular 2. Distributed 3. Discoverable 4. Swappable 5. Shareable

- Interface Abstraction - Modularization

The Gartner SOA Business Case Framework

The goal is to understand, identify and assemble SOA value information to create a business case document. Business Case Document Components of the Framework 1. Elements (30) describe fundamental SOA value Justification propositions and cost areas. 2. Elements are chained together for end-to-end traceability. Profiles 3. Chains are grouped into bundles according to the nature of the SOA Bundles project. 4. Each element has a descriptive profile. Chains 5. Chains and bundles assemble relevant element profiles into SOA Elements justification.

Elements Capture SOA Characteristics

Traceability Traceability
6. 6.SOA SOAPrinciples Principles Modular Modular Swappable Swappable Shareable Shareable Clearly ClearlyDefined Defined Distributable Distributable 3. 3.SOA SOATechnology TechnologyBenefits Benefits
Standardized Systems Integration Standardized Systems Integration Faster Application Development Faster Application Development Enhanced Functionality Evolve-ability Enhanced Functionality Evolve-ability Improved Systems Deploy-ability Improved Systems Deploy-ability Improved Systems Scalability Improved Systems Scalability Better Process Visibility Better Process Visibility Discover Functionality Retirement Discover Functionality Retirement IT Modernization and IT Modernization and Technology Refresh Technology Refresh Legacy Systems Extension Legacy Systems Extension Enhanced Capability Sharing Enhanced Capability Sharing

2. 2.SOA SOABusiness BusinessBenefits Benefits

Business Process Agility Business Process Agility Cost Reduction or Avoidance Cost Reduction or Avoidance Time to New Capability Time to New Capability Business Scalability Business Scalability Increased Business Coordination Increased Business Coordination Enhanced Information Quality Enhanced Information Quality

4. 4.Costs/Risks Costs/Risks
Business Process Management Business Process Management Cost Increases Cost Increases Business Operations Impact Business Operations Impact Organizational Culture Organizational Culture

1. 1.Business BusinessImpact Impact Revenue RevenueGrowth Growth Market MarketShare Share Growth Growth Better BetterProfitability Profitability Competitive Competitive Position Position Regulatory Regulatory Compliance Compliance

5. 5.Costs/Risks Costs/Risks
Services Governance Services Governance Information Security Information Security Systems Management Systems Management End-to-End Performance End-to-End Performance Architecture Effort Architecture Effort Skills Available Skills Available Technology Maturity Technology Maturity Organizational Capabilities Organizational Capabilities

Provides Providesa aframework frameworkfor for targeting targetingapplication applicationchallenges challenges as asSOA SOAopportunities opportunities

The SOA Application Pattern Taxonomy

Separately-defined formal service interfaces Encapsulated (opaque) published software services Driven by openended event notifications

Software as Business Services

Driven by named requests for work

SOA
Request-driven SOA
RPC WOA
Web Services

IDL-based interfaces WS-* or SOAP REST\Web-based interfaces

Event-driven SOA
MQ
Web Services

Pub/Sub
Web Services

Message-style interfaces

WS-Reliable Messaging

WS-Notification or WS-Eventing

Event-object style interfaces

What Is Web-Oriented Architecture (WOA)?

Sub-style of SOA WOA=SOA+www+REST Fundamental REST principles: - Identification of resources - manipulation of resources through representations - hypermedia as the engine of application state - self-descriptive messages - application neutrality
The Hourglass Model of Middle-Out Architecture
Uncertainty Any Web user

Extensible

Generic Systems
Generic
Identifier: URL Simple Format: Atom Interface Protocol: HTTP

Web
- HTTP: Get, Post, Put, Delete - URL addressability - No session state

GET PUT Uncertainty Any Web resource

Federated Components

Advanced SOA: Events, Requests and State

Logical Unit of Work

Start End Request Handler Event Event Notification Handler

Business Process

Advanced SOA Initiatives Require Sophisticated Infrastructure: The SOA Backplane

All-in-One Application Platform Suite

Native SOA Application

Non-SOA Wrapped Application

Services
TPM, EAS

Application Logic
Wrapper Interface Wrapper Interface Wrapper Interface

SOA Backplane
ESB, IS, Appliances Adapters, Programmatic Integration Servers

BPM Application
Portal Product Multichannel

BPM Technology

Portal

Composite Portal Product, EAS, Application/ Mashup Composite Application Tools,

Mashup tools

SOA Without Governance (aka Degenerating SOA)

"Wild West" SOA
The most common case of a degenerated SOA. Services proliferate wildly because no formal service definition process is in place. Frequently fueled by widespread enthusiasm about the ease-of-use of Web services. No central registry; nobody knows how many services are in place, where they are or what they do. Extremely difficult situation to fix and gain control of.

Shelfware SOA
A working SOA is implemented, but few applications actually use the public services. Most applications remain as they are. There's little buy-in from several business units, no agreed-on application architecture companywide and reuse is an unkept promise. The intentions are good, but SOA is a waste of resources and won't deliver benefits.

Duplicated SOA
Slightly more disciplined and more devious version of a Wild West SOA. Simply too large; may contain more than 1,000 services. Although "things work well," many services have significant unplanned duplication Rewarding mechanisms for creating reusable services and reusing established services are vague. Little reuse and maintenance costs multiply. Companies are often reasonably happy with this SOA, even though their savings would multiply if they reduced the level of duplication.

Main RACI Table for SOA Governance

Decision Responsible Accountable
Enterprise Architects Enterprise Architects, CoE Internal Marketing, Process Owners

Consulted
Process Owners, Application Developers, Security Experts,** DB Experts** Process Owners, Application Developers, Security Experts,** DB Experts**

Informed
All CoE

Which services Enterprise Architects, to do? Application Developers Enterprise Architects, Application Developers, Which services CoE Internal Marketing, to do first? Process Owners, SOA Project Sponsor*

All CoE, SOA Project Sponsor

If a new, reusable Application Developers, Enterprise Architects, Enterprise service is agreed, Is this really a Process Owners,* all CoE; if not, CoE Administrators, Architects, new, reusable Integration Tech. Vendors,* service owners Application Developers, CoE service? Security Experts,** of the services Process Owners* Administrators DB Experts** that are reused. Who's going to Enterprise Architects, Process Owners, SOA Project Application pay for the Application Developers, Process Owners, Sponsor, development & Operations, Developers, Application Developers, IT Budget maintenance Security Experts,** Service Owners IT Budget Committee Committee of this service? DB Experts** Enterprise Process Owners, Enterprise Architects, Architects, Application Developers, Who owns All CoE Application Developers, Application Operations, this service? Process Owners* Developers, Security Experts,** Process Owners* DB Experts**

* For coarse granularity, highly reusable services ** Depending on the nature of the service

IT Modernization A Flight to Flexibility

Is IT helping to improve business results in existing markets?

Is IT producing the right level of performance at a competitive price? Can IT help the business move to new markets ?

The Pace of Change for Modernization

IT Drivers Staffing, Skills Consolidation Agility/need for speed Market Drivers Social Networking Consumerization Green Business

Technology Drivers Virtualization is everywhere SOA Initiatives Facilities and Infrastructures Packaged Applications

IT Modernization The Domino Effect

Finding and fixing the Dominos
Trinity Millennium Group BluePhoenix Speedware HP Microsoft Micro Focus Oracle
Aging IT infrastructures and applications, coupled with an increased need to be responsive to business demands have forced many organizations to rethink traditional incremental technology improvement programs and focus on a holistic IT Modernization program.

TSRi

14

Software Development: The Future is Now

~250 Billion lines of legacy code, 200 million lines of Cobol. The Services being built today will last for. >10K Facebook Applications, Force.Com, Amazon Web Services are available today
Long-term Impact of Short-term Actions

Gartner's Maturity Model for Application Organizations

Level 1 Level 2 Level 3 Level 4 Quantitatively Level 5

Ad Hoc
High

Repeatable

Defined

Optimizing
Process limitations recognized Clear improvement responsibility assigned Consistently, reliably and regularly improves based on measures Interdependency among disciplines is essential

Managed
Measures indicate process performance Identifies gaps Automated process generates data for measures Interdependency among disciplines emerges

Maturity
Teams establish processes Repeatable within team Little crossdiscipline activity

Low

Processes not specified Individuals determine Reinvent wheel each time

Processes defined and documented Consistently followed across the organization Little rework Synergy among disciplines strengthens

APPLES VERSUS ORANGES

Legacy Versus New Dev Platforms, circa 2010

Senior Developer
Amazon Web Services Force.com Yahoo
Pipes LAMP (PHP, RoR)

Java EE

Google App Engine

Junior Dev

VB.Net

VB6

Power User

Excel with Macros

Microsoft
Popfly

Google Docs?

Legacy Apps

Hybrid or Mashed Up

New Apps

Recommendations
Treat SOA as a strategic initiative. Justify and measure SOA success Use a systematic approach to designing services
for particular and extended use. Advance gradually through SOA stages of maturity. Establish a competency center to coordinate SOA efforts. Address SOA as part of an IT modernization effort Explore new development methods to achieve the agility and sharing benefits of SOA