2. Motivation
• This is an intensive workshop which aims to build enough
knowledge and understanding among software architects to be
able to start building a service oriented architecture without
making the common mistakes.
• This workshop builds upon a three-day workshop run at many big
companies but compressed hard to make time for more design-
time service policy discussions as signalled beeing important to
Canal Digital.
3. Goal
• Get an understanding of how and why Soa projects fail
• Understand some of the key building blocks neccessary to
build successful SOAs
• Learn how to think about SOA
3
4. Goals
• Totto's ambiguous goals
– Introduce and understanding of the huge untapped potential of
customer and project value in SOA projects
– Introduce the key concepts and how they fit nicely together to
allow you to lead customers and projects in the right direction
– Introduce a well defined model for discussing and
communicating SOA, services and governance
– Leave you capable of solving ANY SOA challenge
5. Agenda
SOA in «2» slides
• Motivation
• Agenda
• SOA in 3 slides
• Laws of SOA
• Real SOA versus Same Old Architecture,
• SOA Maturity Model
• Some examples of HOW successful SOA provides real value
5
9. Laws of SOA
0. Forget about focusing WS and products
1. Establish service categories and service universe
2. Find and decompose services
3. Establish service ownership and Key Performance Indicators for your
services
4. Establish design rules for your service categories up-front
5. Start limited and controlled
6. Establish lean and agile deployment routines
7. Versioning is not optional in SOA
8. Security is not optional in SOA
9. Reflect and work strategically against SOA Maturity Model.
9
10. Normal SOA
• Most SOA projects fail
– Most quoted figures are about 80%
• The ”successful” SOA projects usually
archieve value comparable with
technology refreshes as seen in this
figure
• This is itself a failure to deliver the on
the promisses of SOA and is the result
of what is popular called «Same Old
Architecture..”
10
11. “Real value” SOA
• understand the concept of a service
• Service Manifest
• services as good building-blocks
• categorizing your services
• requirements and rules for the different
categories of services
• Design-Time Governance
11
But today we are talking about how to achieve this target
13. Design Time Governance
All CS and ACS services complies to sets of core governance
policies, including;
• Implements same patterns
• Complies to same request response patterns
• Supports evolve ability
• Coherent failover and operational capabilities
• Ensures great service through a common usage pattern
across +15 services in first phase delivery
13
15. SOA – hype? (Anno 2007)
15
Hype
Business value
WS-*
CFX/
XFire
SAML 2.0
OW
SOA
EDR
Tjeneste
kategorisering
Mule
REST
ESB
Endpoint
Design-time
Governance
AXIS
Web
Services
WS
ducktyping
ESE
Run-time
Governance
Governance
PAB
BAM
16. “Real value” SOA
• Key areas
– Understanding services and how they are different
– Successful services and the service universe
– Learn of the different technical types of services and how they
apply to your business services
– Ownership, value, KPI and governance of services
– Re-introduce Business Objects as first-class inhabitants in
your architecture
– Learning/leading versus managing/controlling
Pust ut – Senk skuldrene
17. Credits and key contributors
• Mads Nissen (Puzzlepart)
• Objectware Community Wiki
• Cantara Community Wiki
• Bård Lind (Telenor)
• Mark West (Bouvet)
• Lars Flågan (LUUP)
• Øystein Garshol (Puzzlepart)
• Kjartan Aanestad (Webstep)
• Kaare Nilsen (Arktekk)
• Kristoffer Moum (Zenior)
• Johannes Brodwall (Steria)
Pust ut – Senk skuldrene
