1 / 24

Patterns for SOA Success

Kris Horrocks Sr. Technical Product Manager Microsoft. Patterns for SOA Success. Patterns and guidance for:. Governance: Runtime Policy Enforcement Service Lifecycle Management Service Versioning. Runtime Policy Enforcement. Governance A Multi-vendor Reality.

johana
Download Presentation

Patterns for SOA Success

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Kris Horrocks Sr. Technical Product Manager Microsoft Patterns for SOA Success

  2. Patterns and guidance for: Governance: Runtime Policy Enforcement Service Lifecycle Management Service Versioning

  3. Runtime Policy Enforcement

  4. GovernanceA Multi-vendor Reality “Through 2011, 65% of companies deploying SOA governance technologies will not acquire those technologies from the preferred vendor of their SOA infrastructure (0.8 probability).” GartnerCriteria for Evaluating a Vendor's SOA Governance Strategy

  5. Policy Management/Enforcement Today • Adding another inf. layer for each policy type doesn’t scale. • Have to crack the message at each layer. • Decrypt • Parse • Identity & access • … • Management is siloed • Difficult to get comprehensive view Consumer Access Policy Infrastructure Data Protection Policy Infrastructure Audit Policy Infrastructure Service

  6. Endpoint Policy Enforcement • Supports multi-vendor infrastructure • Only crack the message once • Depends on ISVs hooking into endpoint model • Assumes you control the endpoint architecture • Requires unique implementation on each service platform • Policy management is still siloed – no common repository Consumer Repositories Tools Service Endpoint Apply Access Policy Apply Data Protection Policy Apply Audit Policy

  7. Heterogeneous Policy Management • Still supports multi-vendor infrastructure • Management consolidation around role • Depends on ISVs federating with shared repository Consumer FederatedRepositories Tools Service Endpoint Apply Access Policy Apply Data Protection Policy Apply Audit Policy

  8. Service Lifecycle Management

  9. Service Lifecycle Management ProviderALM ConsumerALM

  10. Service Lifecycle Management SLM ProviderALM ConsumerALM It’s not about bits. It’s about the relationship...

  11. Service Lifecycle Management SLM ProviderOrganization ConsumingOrganization Ownership Boundary … across an organizational boundary.

  12. Organizational Negotiations SLM ProviderOrganization ConsumingOrganization Ownership Boundary Version Availability Instance Availability Business Policy Technical Policy

  13. Service Versioning

  14. Service Versioning UI UI Logic Logic Application Owner Data Data Application Owner

  15. WSDL Boundaries • Service boundaries are often arbitrary or usage-specific, yet they are tightly coupled • Web Services = some collection of operations at an endpoint • WSDL is a collection of contracts • Web Services specs should continue to be leveraged to support and promote interoperability • Just need more flexibility and control

  16. Service Virtualization

  17. Virtual Reality • Virtualization is being applied to many scenarios • Virtual Machines (Mobile, Desktop, Server) • Virtual Storage (SAN, Snapshots) • Virtualization adds significant value • Service virtualization takes loose coupling one step further • Services typically are composed of two sets of code: • Code required to execute business functions • Code required to execute policies and behavior

  18. Server Virtualization

  19. Service Virtualization

  20. Implementation Pattern Service Repository

  21. Implementing Service Virtualization • Building blocks emerging • Service Repository • Service Runtime Engine • Metadata has been effective in enabling service virtualization • The “right” meta data is key • Support design time processes • Execute appropriate behavior at runtime

  22. Managed Services Engine “The MSE fully enables service virtualization through a Service Repository, which helps organizations deploy services faster, coordinate change management, and maximize the reuse of various service elements. The MSE provides the ability to support versioning, abstraction, management, routing, and runtime policy enforcement for Services.” • CodePlex Download (http://www.codeplex.com/servicesengine) • Service Repository • Runtime Engine • MMC SnapIn • Service Test Client • Technical Guide • Walkthrough Guide

  23. Summary • Service virtualization is a critical component for enterprise SOA • Design time and runtime support of meta data is key for service virtualization • Platform provides core capabilities to support and augment virtual services • The Managed Services Engine (MSE) can accelerate SOA implementations today

  24. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related