More Related Content Similar to Principles of Service-Oriented Architecture (20) More from Douwe Pieter van den Bos (11) Principles of Service-Oriented Architecture2. Introduction
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 2
3. What do we need to know to design an
(Service-Oriented) Architecture?
| Capgemini The Netherlands – Oracle Solutions
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. Why do we want
Service-Oriented Architecture?
| Capgemini The Netherlands – Oracle Solutions
6. Reducing Costs
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 6
7. Agility
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 7
9. Time-to-market
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 9
10. Consolidation
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 10
11. Alignment
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 11
13. Layers
© The Open Group | Capgemini The Netherlands – Oracle Solutions
SOA Reference Architecture
© 2011 Capgemini. All rights reserved. 13
14. Maturity
© The Open Group | Capgemini The Netherlands – Oracle Solutions
SOA Maturity Model
© 2011 Capgemini. All rights reserved. 14
15. What do we need to achieve this?
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 15
16. 8 Principles
Standardized
Loosely Coupled
Reusable
Composable
Autonomic
Stateless
Abstract
Discoverable
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 16
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. Loosely Coupled
Independent Design & Evolution
Decouples from Environment
Interoperability Guaranteed
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 18
19. Reusable
Reuse & Multi-Purpose of:
• Resources
• Logic
• Functionality
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 19
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. Autonomic
Less (/ No) Dependencies
Increases Reliability
Predictable Behavior
Control over Resources
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 21
22. Stateless
Needed to increase:
• Scalability
• Availability
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 22
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. Discoverable
No Secret
Easy Identification
Optimizes Reuse
| Capgemini The Netherlands – Oracle Solutions
© 2011 Capgemini. All rights reserved. 24
25. More information
Please 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
Editor's Notes 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”