• Save
Principles of Service-Oriented Architecture
Upcoming SlideShare
Loading in...5
×
 

Principles of Service-Oriented Architecture

on

  • 7,250 views

Session given on february 21st 2012 on Principles of Service-Oriented Architecture for the Oracle Division of Capgemini The Netherlands

Session given on february 21st 2012 on Principles of Service-Oriented Architecture for the Oracle Division of Capgemini The Netherlands

Statistics

Views

Total Views
7,250
Views on SlideShare
6,629
Embed Views
621

Actions

Likes
11
Downloads
0
Comments
1

4 Embeds 621

http://www.ome-b.nl 452
http://apex.collected.info 165
http://xss.yandex.net 3
http://theoldreader.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Please sent this file to my mail id
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • My name is Douwe Pieter van den Bos. I’m the Thoughtleader Oracle Service-Oriented Architecture at Capgemini The Netherlands. Since 2010 I’m an Oracle ACE. I’m a published author at Packt Publishing and have presented at various international conferences, like Oracle OpenWorld.
  • There are,like in every design, 6 questionsthat we need to askourselves.
  • This model shows us the service layers as the SOA ReferenceArchitecture, courtesy of The Open Group, desrcibes.
  • A SOA isn’tachieved withoutstrugle, and notwithin a short amount of time. It’s a model anorganizationneeds to growinto, the complete organizationneeds to mature. The Open Group SOA Maturity Model describeswhere the maturity is found and howitcanbeachieved.The onlyway to “go-SOA” is by “Baby steps”

Principles of Service-Oriented Architecture Principles of Service-Oriented Architecture Presentation Transcript

  • Principles of Service-Oriented ArchitectureDouwe Pieter van den BosUtrecht, February 21st 2012
  • Introduction | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 2
  • What do we need to know to design an (Service-Oriented) Architecture? | Capgemini The Netherlands – Oracle Solutions
  • 6 W’s Who?  … benefits from a SOA?  … is responsible for the SOA? What?  … is a SOA?  … are Services? Where?  … in the organization do we implement a SOA?  … in the process … When?  … in time do we implement a SOA?  … is an organization mature enough for a SOA? How?  … does the technology work?  … much will it cost? Why?  … do we need to implement the SOA? | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 4
  • Why do we wantService-Oriented Architecture? | Capgemini The Netherlands – Oracle Solutions
  • Reducing Costs | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 6
  • Agility | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 7
  • Increasing Competitive Advantage | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 8
  • Time-to-market | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 9
  • Consolidation | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 10
  • Alignment | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 11
  • What isService-Oriented Architecture?
  • Layers © The Open Group | Capgemini The Netherlands – Oracle SolutionsSOA Reference Architecture © 2011 Capgemini. All rights reserved. 13
  • Maturity© The Open Group | Capgemini The Netherlands – Oracle SolutionsSOA Maturity Model © 2011 Capgemini. All rights reserved. 14
  • What do we need to achieve this? | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 15
  • 8 Principles Standardized Loosely Coupled Reusable Composable Autonomic Stateless Abstract Discoverable | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 16
  • Standardized Need to operate beyond: • Technologies • Environments • Knowledge Ensures: • Consistency • Reliability • Governance | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 17
  • Loosely Coupled Independent Design & Evolution Decouples from Environment Interoperability Guaranteed | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 18
  • Reusable Reuse & Multi-Purpose of: • Resources • Logic • Functionality | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 19
  • Composable Combine in order to create. Break up into smaller parts. Less Complexity. Supports Growth. Compose versus Build | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 20
  • Autonomic Less (/ No) Dependencies Increases Reliability Predictable Behavior Control over Resources | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 21
  • Stateless Needed to increase: • Scalability • Availability | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 22
  • Abstract “No one needs to know what’s under the hood…” Enables “”Loosely Coupled” Makes Granularity Possible It offers possibilities to grow and mature without consumer intervention | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 23
  • Discoverable No Secret Easy Identification Optimizes Reuse | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 24
  • More informationPlease contact:• Douwe Pieter van den Bos douwe-pieter.vanden.bos@capgemini.com +31 6 203 623 88 | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 25
  • www.capgemini.comThe information contained in this presentation is proprietary. ©2010 Capgemini. All rights reserved