Mark Gilbert Microsoft Corporation

Services Taxonomy Building Block Services Attached Services Finished Services

WPF

Consumer Services Have … Pushed the Operational Scale Changed the Economics of Computing Simplified the Delivery of New Software Increasing Core Counts Virtualization Extreme Mobility The Drivers – What is Causing the Change

A Look at Services Today Messenger: over 280 million active accounts Spaces: over 130 million unique users worldwide Search: index of more than 5 billion documents and 400 million images MSN: over 465 million unique visitors worldwide Hotmail: over 285 million active accounts Office Live Small Business: over 450k business subscriptions

1.New Capabilities 2.Time to Deliver 3.Cost Adoption Drivers

The Next Phase in Evolution MainframePC Client Server SOAScale-OutService

Total Cost of Ownership Complex and Specialized Knowledge to Provision Upgrade costs and time Lack of Business Agility and Flexibility Disparate Systems Software Challenges Today

Software Evolution

SOA Evolution - Single Instance to Scale Out

Substantially Reduced Cost Reliability on Stock Hardware Essentially Infinite Scale for Most Applications What Does This Give Us 24x7 Operations 8x5 Operations with 24x7 Reliability

No instance reliability Needed state must be written to service or multiple peers Backwards/forwards compatible +- 1 version Multiple Versions Must Live SxS Error recovery is the main (and only) startup case Consider your applications characteristics At What Cost to Software

Consistency – Get after a Put should reflect the update Availability – Incoming requests should be served and receive a response in a timely manner Partition Tolerance - The service functions when part of a network or machine fails Pick Two of the Three Brewer’s Principle

Evolution Toward Services  Utilizes the underlying services and infrastructure in the data center  Leverages other services  Offers new functionality with composite services  Has a customization platform Hosting the on-premises app SimulatingMulti-tenancy Re-architecting for “the cloud” Utilizing a services platform  8x5 operations  Multi-tenancy  Scale-out management & provisioning  Automatic error handling  Self-service on- boarding  Optimizes shared infrastructure for critical resource(s)  Establish best practices  Understand management shortcomings  Role key changes back into the product  Connected to a service delivery infrastructure  Integrated automated systems  Some components are self-service Phase 1 Phase 2 Phase 3 Phase 4

Extending the Microsoft Platform ServerServiceClient

NETWORKING COMPUTING STORAGE What Is a Service Platform Identity, Directory & Access Control Data Communications Essentials Building Blocks Finished & Attached Services Finished & Attached Services Online

And Unique Service Capabilities Customer Provisioning Accounts & Billing Logging & Monitoring SLA & Business Model

Faster time to market Lower OPEx and CAPEx Dramatic reduction in infrastructure Focus on customer value, not plumbing Leverage existing skills, code, investments Enable new scenarios An Equalizer between big and small companies Why A Platform?

Scale-out Reliable Platform Common capabilities that span clients, servers and cloud Consistency and Interoperability between On-Premises and our Services Enterprise quality and compliance, SLA availability Partners are Important at All Levels Service Platform Principles

Example ESB to ISB Firewall

Every Level Finished Services Attached Services Building Block Services Operations Architectural and Development Expertise On-boarding and Off-boarding Partners

Microsoft’s Strategy

Thank you