ibm software group ® soa – successful adoption and barriers idc service-oriented architecture...

IBM Software Group

®

SOA – Successful Adoption and Barriers

IDC Service-Oriented Architecture Conference 2005

Rick Robinson, IT Architect, IBM EMEA WebSphere Lab Services

[email protected]

IBM Software Group | WebSphere software

Agenda

What works?

Barriers

Roadmaps

Summary

IBM Software Group

®

What Works?

Business scenarios, technologies and governance


What Works? Business Scenarios

Multi-channel Multiple technology channels, e.g. desktop, browser pervasive

Multiple brands

Intermediary, B2B or dot.com models Small to large

Service aggregation e.g. financial portals

dot.com integration e.g. Amazon, e-Bay

New Applications Well-targetted process automation

Integration or Consolidation Bottom-up integration architectures of reasonable ambition

Single view of data


Legacy e.g. CICS “routing transaction” using simple structured data formats

… increasingly migrating to Web services

Enterprise Application Integration (EAI) XML interfaces and message formats

Communication through EAI technology e.g. asynchronous messaging

Custom API frameworks provide application support

… increasingly migrating to Web services

Web services Many current uses of Web services are for basic point-to-point integration

Some more advanced organisations have built SOA infrastructures with extensive use of Web services

… becoming more common as Web services mature

What Works? Technologies


Reseller channels, e.g. supermarkets

Branches

Online bank

Corporate Bank

... etc. ...S

ervi

ce G

atew

ay Account Management

Payments

etc.

Operations Director

Cha

nnel

Ow

ners

System

Ow

ners

What Works? Aligned Service and System Ownership

One layer of services Organisation matches service architecture Obvious owners of services and supporting infrastructure

IBM Software Group

®

Barriers

Mismatches, trust and … governance


Barriers: Mismatches

Narrow drivers, broad ambition Are current business goals to reduce cost or develop new business?

Is the level of sponsorship consistent with the scope of impact?

Inappropriate combinations of risk Pilot project, new technology

Production project, conservative technology

Many other combinations!

Scepticism – adopting SOA successfully requires cultural change “It’s nothing new”

“The technology doesn’t work”

“It’s not for us”


Barriers: Trust

Application

Service 1 Service 2

Change to irrelevant optional schema

Service 3Service Z

No need to test No need to testTest

If SOA uses intermediaries to insulate service consumers from changes to service

implementations, how do services consumers know when to re-test?

Until services are trusted, regression testing will be performed in all cases Automated testing scripts and tools can be used to minimise impact

Change to relevant optional

schema or mandatory

schema

Service implementation

changed or substituted


Barriers: Governance

Store Client (Catalogue)

Sales Management Client

Store Client (Orders)

Product Management Client

... etc. ...

Ser

vice

B

us

Order Services

Product Services

etc.

Pricing Services

Accounts

Product Management

etc.

ERP

No clear point of ownership for common services Infrastructure owned by IT, clients and back end systems owned by lines of business Tends to result in a proliferation of variations of “common” services dedicated to specific

channels


ITASOA Project

Barriers: Governance

!

ITS

InfrastructureCan it be operated

?

Architecture Review Board

OperationalTDA

Does it advance our strategy?

Enterprise Architecture Group

Our strategy is SOA

I need a new mortgage system

IBM Software Group

®

Roadmaps


There is no roadmap …

Standards Based Model for all Service Interaction Aspects Important aspects include protocols, interface definitions, message formats, APIs, directories

etc.

Service Enable Legacy Systems and Applications Analogous to JDBC enablement of databases for J2EE

Implement a High Quality of Service Infrastructure Asynchronous messaging, assured delivery, security, transactions and compensation etc.

Establish a comprehensive model and implementation of different types of service Business process vs. business transaction vs. technical service vs. external service vs. legacy

service etc.

Service directory and re-use strategy Establishing the development culture, publishing and discovering services, internally and

externally etc.

Establish organisations and processes for governance and ownership Enterprise Architecture governance, service ownership etc.

… but there are many individual steps to take in an order that makes sense to your organisation.

IBM Software Group

®

Summary


Summary

SOA has been repeatedly proven over the last decade (at least!)

Open standard and product support is increasingly rapidly in sophistication and maturity

In it’s broadest form, SOA is an approach to Enterprise Architecture, and there is no skirting the difficult issues associated with that

But a big-bang approach is not mandated …

… a flexible, incremental approach moulded to business needs and strategy is the most likely to succeed

IBM Software Group

®

End


Timings

3 minutes intro 3 slides in first section finish on 5, 7, 9 minutes 1 minute bridge 4 slides in second section finish on 12, 14, 16, 18 minutes 1 minute bridge 1 slide in last section finishes on 21 minutes 4 minutes wrap-up and contingency

ibm software group ® soa – successful adoption and barriers idc service-oriented architecture...

Documents

ibm software group roadmaps

service ownership

legacy service

service consumers

technical service

external service

service z

service directory