introducing managed services wolf gilbert architect evangelist microsoft corporation

Introducing Managed Introducing Managed ServicesServices

Wolf GilbertWolf GilbertArchitect EvangelistArchitect EvangelistMicrosoft CorporationMicrosoft Corporation

Value of Service Enablement

Reach, Reuse and Manageability are key to success in the Enterprise

Previous efforts focused on Reuse and some Reach

Success with Reach and Reuse leads to more difficulty with Management

Explicit Machine Readable PolicyMove "policy" issues out of code -> be more productive

Must treat Services as a SystemDifficult to even talk about with out a Model

Enterprise Service Orientation Maturity Model (ESOMM)

Maturity Models descend from Carnegie Mellon’s CMM

Some current “SOA Maturity Models” move Best Practices instead of Best Principles

CMM was process focused because it was a Maturity Model for the Software Development Process

Levels in a Maturity Model should be Self-Evident

The levels are only useful in so much as they define “meaningful” states.

Maturity Models should be PrescriptiveNeed to show where you are, where you wish to be and how to get there.

ESOMM Maturity Levels

Enterprise is capable of writing and consuming standards conformant Services with excellent reach

Enterprise implements, consumes, and reuses Services efficiently and consistently

Enterprise can effectively Manage and Support large numbers of Services with guaranteed SLA's

Enterprise is capable of aggregating Services and extending their use beyond its own borders

ESOMM PerspectivesIImplementatimplementati

onon ConsumptioConsumptionn

AdministratiAdministrationon

ESOMM CapabilitiesImplementatiImplementati

onon ConsumptioConsumptionn

ServiceCollaboration

Service Orchestration

ExternalPolicy

ServiceSDK's

BusinessAnalytics

AutomatedPolicy Mgmt

SchemaBank

Runtime Policy

Versioning

ExecutionVisibility

Explicit SLA’s

Service Portal

Auditing

ProvisioningModel

AdvancedMonitoring

CommonSchema

ServiceBlocks

Self Provisioning

Service Discoverability

EnterprisePolicies

DeploymentManagement

Development Processes

Design Patterns Testability

Explicit Contracts

Basic Monitoring

Security Model

AdministrationAdministration

Key Challenges

WSE 2.0/WSE 3.0/WCF/Brand X Toolkit IncompatibilitiesService GranularityService VersioningManaging Policy ChangesService Level MonitoringTestabilityScalability

Managed ServicesServices as a System

Service is entirely VirtualThe "Operation" is really the "Service“

Service Definition (interface) distinct from Service Implementation

Service Definition Consists of Four Parts:

Endpoint; Message; Policy; Context (Intent + State)

The "Service Network" requires a "Runtime Engine"

Executable Policy; Schema Bank; Service Blocks; etc.

Topology is an implementation detailThis isn't about the ESB!

Managed Services Engine Reference Architecture

The Managed Services Engine

processes Service Requests with

Messaging, Brokering, and Dispatching..

© 2005 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.