Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Principles of Service-Oriented ArchitectureDouwe Pieter van den BosUtrecht, February 21st 2012
Introduction               | Capgemini The Netherlands – Oracle Solutions                                  © 2011 Capgemin...
What do we need to know to design an     (Service-Oriented) Architecture?                        | Capgemini The Netherlan...
6 W’s Who?  … benefits from a SOA?  … is responsible for the SOA? What?  … is a SOA?  … are Services? Where?  … in...
Why do we wantService-Oriented Architecture?                | Capgemini The Netherlands – Oracle Solutions
Reducing Costs                 | Capgemini The Netherlands – Oracle Solutions                                    © 2011 Ca...
Agility          | Capgemini The Netherlands – Oracle Solutions                             © 2011 Capgemini. All rights r...
Increasing Competitive Advantage                             | Capgemini The Netherlands – Oracle Solutions               ...
Time-to-market                 | Capgemini The Netherlands – Oracle Solutions                                    © 2011 Ca...
Consolidation                | Capgemini The Netherlands – Oracle Solutions                                   © 2011 Capge...
Alignment            | Capgemini The Netherlands – Oracle Solutions                               © 2011 Capgemini. All ri...
What isService-Oriented Architecture?
Layers   © The Open Group          | Capgemini The Netherlands – Oracle SolutionsSOA Reference Architecture               ...
Maturity© The Open Group     | Capgemini The Netherlands – Oracle SolutionsSOA Maturity Model                             ...
What do we need to achieve this?                             | Capgemini The Netherlands – Oracle Solutions               ...
8 Principles Standardized Loosely Coupled Reusable Composable Autonomic Stateless Abstract Discoverable           ...
Standardized Need to operate beyond:  • Technologies  • Environments  • Knowledge Ensures:  • Consistency  • Reliability...
Loosely Coupled Independent Design & Evolution Decouples from Environment Interoperability Guaranteed                  ...
Reusable Reuse & Multi-Purpose of:  • Resources  • Logic  • Functionality                                         | Capge...
Composable Combine in order to create. Break up into smaller parts. Less Complexity. Supports Growth. Compose versus ...
Autonomic Less (/ No) Dependencies Increases Reliability Predictable Behavior Control over Resources                  ...
Stateless Needed to increase:  • Scalability  • Availability                                    | Capgemini The Netherlan...
Abstract “No one needs to know what’s under the hood…” Enables “”Loosely Coupled” Makes Granularity Possible It offers...
Discoverable No Secret Easy Identification Optimizes Reuse                                       | Capgemini The Nether...
More informationPlease contact:• Douwe Pieter van den Bos  douwe-pieter.vanden.bos@capgemini.com  +31 6 203 623 88        ...
www.capgemini.comThe information contained in this presentation is proprietary. ©2010 Capgemini. All rights reserved
Upcoming SlideShare
Loading in …5
×

Principles of Service-Oriented Architecture

13,342 views

Published on

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

Published in: Technology, Business

Principles of Service-Oriented Architecture

  1. 1. Principles of Service-Oriented ArchitectureDouwe Pieter van den BosUtrecht, February 21st 2012
  2. 2. Introduction | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 2
  3. 3. What do we need to know to design an (Service-Oriented) Architecture? | Capgemini The Netherlands – Oracle Solutions
  4. 4. 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
  5. 5. Why do we wantService-Oriented Architecture? | Capgemini The Netherlands – Oracle Solutions
  6. 6. Reducing Costs | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 6
  7. 7. Agility | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 7
  8. 8. Increasing Competitive Advantage | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 8
  9. 9. Time-to-market | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 9
  10. 10. Consolidation | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 10
  11. 11. Alignment | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 11
  12. 12. What isService-Oriented Architecture?
  13. 13. Layers © The Open Group | Capgemini The Netherlands – Oracle SolutionsSOA Reference Architecture © 2011 Capgemini. All rights reserved. 13
  14. 14. Maturity© The Open Group | Capgemini The Netherlands – Oracle SolutionsSOA Maturity Model © 2011 Capgemini. All rights reserved. 14
  15. 15. What do we need to achieve this? | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 15
  16. 16. 8 Principles Standardized Loosely Coupled Reusable Composable Autonomic Stateless Abstract Discoverable | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 16
  17. 17. Standardized Need to operate beyond: • Technologies • Environments • Knowledge Ensures: • Consistency • Reliability • Governance | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 17
  18. 18. Loosely Coupled Independent Design & Evolution Decouples from Environment Interoperability Guaranteed | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 18
  19. 19. Reusable Reuse & Multi-Purpose of: • Resources • Logic • Functionality | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 19
  20. 20. 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
  21. 21. Autonomic Less (/ No) Dependencies Increases Reliability Predictable Behavior Control over Resources | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 21
  22. 22. Stateless Needed to increase: • Scalability • Availability | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 22
  23. 23. 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
  24. 24. Discoverable No Secret Easy Identification Optimizes Reuse | Capgemini The Netherlands – Oracle Solutions © 2011 Capgemini. All rights reserved. 24
  25. 25. 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
  26. 26. www.capgemini.comThe information contained in this presentation is proprietary. ©2010 Capgemini. All rights reserved

×