Introduction, background and why Service
Oriented Architecture
Totto
Motivation
• This is an intensive workshop which aims to build enough
knowledge and understanding among software architect...
Goal
• Get an understanding of how and why Soa projects fail
• Understand some of the key building blocks neccessary to
bu...
Goals
• Totto's ambiguous goals
– Introduce and understanding of the huge untapped potential of
customer and project value...
Agenda
SOA in «2» slides
• Motivation
• Agenda
• SOA in 3 slides
• Laws of SOA
• Real SOA versus Same Old Architecture,
• ...
Schedule
6
SOA IN 2 SLIDES
What nobody seems to understand, and still remains the
most important aspects of success with Service Orie...
8
Laws of SOA
0. Forget about focusing WS and products
1. Establish service categories and service universe
2. Find and deco...
Normal SOA
• Most SOA projects fail
– Most quoted figures are about 80%
• The ”successful” SOA projects usually
archieve v...
“Real value” SOA
• understand the concept of a service
• Service Manifest
• services as good building-blocks
• categorizin...
SOA Maturity
Models
Level 2Level 2
Level 2
SOAMM
•..
•..
•2: Data
•1: Design
•0: Chaos
Design Time Governance
All CS and ACS services complies to sets of core governance
policies, including;
• Implements same ...
Real-time enterprise.. Just a dream?
EDR-MDS Enterprise
Search
EDA
Realtime
BI
EDR-MDS
EDR-MDS
SOA – hype? (Anno 2007)
15
Hype
Business value
WS-*
CFX/
XFire
SAML 2.0
OW
SOA
EDR
Tjeneste
kategorisering
Mule
REST
ESB
E...
“Real value” SOA
• Key areas
– Understanding services and how they are different
– Successful services and the service uni...
Credits and key contributors
• Mads Nissen (Puzzlepart)
• Objectware Community Wiki
• Cantara Community Wiki
• Bård Lind (...
LETS GET STARTED!!
18
Upcoming SlideShare
Loading in …5
×

laws of SOA

350 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
350
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

laws of SOA

  1. 1. Introduction, background and why Service Oriented Architecture Totto
  2. 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. 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. 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. 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
  6. 6. Schedule 6
  7. 7. SOA IN 2 SLIDES What nobody seems to understand, and still remains the most important aspects of success with Service Oriented Architecture 7
  8. 8. 8
  9. 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. 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. 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
  12. 12. SOA Maturity Models Level 2Level 2 Level 2 SOAMM •.. •.. •2: Data •1: Design •0: Chaos
  13. 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
  14. 14. Real-time enterprise.. Just a dream? EDR-MDS Enterprise Search EDA Realtime BI EDR-MDS EDR-MDS
  15. 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. 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. 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
  18. 18. LETS GET STARTED!! 18

×