1. Rethinking Infrastructure Architecture: Service Oriented Infrastructure Kevin Sangwell Infrastructure Architect Microsoft EMEA HQ

2. The Organic Infrastructure CRMERP Financial Portal Document Mgmt 5 Separate Web Farms 5 Separate SQL Environments 5 Separate Identity Stores

3. The Organic Infrastructure CRMERP Financial Portal Document Mgmt IT Pain Separate Identity Stores Separate and inconsistent Security Separate Config and Deployment Separate Resilience/Load Balancing Separate Monitoring and Management

4. The Organic Infrastructure CRMERP Financial Portal Document Mgmt Poor user experience Confusing array of usernames & passwords Infrastructure gaps obvious to users My information is different across systems It takes weeks for me to get access to everything I need Stuff is slow

5. Consolidation is the answer, right? Reduces number of stove pipes, but doesnt solve them Next application/project adds another stovepipe I think of this as backwards consolidation Doesnt change thinking

6. SOI: What it looks like Identity Management & Monitoring Database File Email Collaboration Web Hosting Services DeploymentSecurity Backup & Recovery PKIDRMiddleware Remote Access and more.. LDAP Authn Authz Audit Provisioning De-Provisioning Federation Self Service …

7. SOI: What it looks like Identity Management & Monitoring Database File Email Collaboration Web Hosting Services Subscribers CRM Publishers Portal

8. Getting There Define & Prioritise Services Define EnterpriseConsumer Experience Define Enterprise Consumer Experience Plan Forward & Backward Consolidation Transition to Service Management

9. Define & prioritise services according to ROI Put low hanging fruit at the top The difference between centralised and service-oriented is shared service Define & Prioritise Services

10. Good candidates Identity Management / Directory Web Hosting Database File store Define & Prioritise Services

11. If IT infrastructure is obvious to the business = poor perception of IT IT Infrastructure is not designed around users Seek to improve Enterprise user experience Unified view (network drive, published printers) Single sign-on Location independence/roaming User Subscriber experience Define EnterpriseConsumer Experience Define Enterprise Consumer Experience

12. Forward consolidation for each service Attach to Projects Major pain/cost areas such as IDM Plan Forward Consolidation Project 1 Web Hosting Requirements New Web Farm as a service Project 2 Additional Hosting Requirements Increase capacity

13. Forward consolidation The future is difficult to predict - what i/o, RAM, CPU will my future application need … so Abstract & Standardise Categorise subscribers as High, Medium or Low Capacity (storage & bandwidth) Load (concurrency / transactions) Performance (responsiveness / user expectations) Availability Implement Standard platform (hardware/software) for each of above When youre defining services in the application architecture domain (SOA) you should be doing this already.

14. Backward consolidation Low hanging fruit Challenges QOS: many services dont support QOS Plan Backward Consolidation File, Print Messaging Databases Easy Hard Technology enabled Process enabled

15. Assign Service Manager for each service Owns relationship with other services SubscribersPublisher Service Delivery Service Level Management Service Level Management Capacity Management Capacity Management Availability Management Availability Management IT Continuity Management IT Continuity Management Financial Management Financial Management Service Support Transition to Service Management

16. Blockers TechnologySecurity Regulatory & compliance Aim to centralise these instead of service- orient them

17. SOI Enablers/facilitators Virtualisation is your friend, and your enemy But doesnt solve all problems: remember virtual hosts still need managing & are lower performance Clustering Cost of resilience reduces with addition of services SAN Flexibility; capacity, replication, backup Evaluate on a case-by-case Slower than DAS Some applications dont support SAN replication/backup

18. An Example: File & Print Easy for central sites: clusters Difficult for branch: Either centralise & cache or replicate data Migrate users to DFS for its location-awareness & server abstraction Fileserver Migration Toolkit does the legwork Dont forget this is a service; apps can consume Benefits Reduces backup pain Easier to manage/apply policies/report on Easy to add resilience & DR support

19. Example: Identity Management Service Define Service: Single directory of users for authentication and access control User Experience Transparency (SSO, location independence, discoverability) Subscriber Experience (Capabilities) LDAP Directory (e.g. AD) Authentication (LDAP Bind, NTLM, Kerberos) Authorisation (Group membership) Auditing (directory access)

20. Example: Identity and Access Management Design Logical Service CapacityPerformanceScalability Backup & DR Security Extensibility for subscribers Design Physical Service Server sizes Server locations

21. Extensibility Remember blockers? Technology (Schema) Regulatory (Forest) Security (Account Policies)

22. Example: Identity and Access Management Service Evolution Move to Identity Management Service Provisioning/de-Provisioning triggered from HR database Federation User Self Service All subscribers benefit from these capabilities

23. Does SOI really have an ROI Basic Rationalized Virtualized Service- Based Standardized Infrastructure resources pooled Services managed holistically Uncoordinated infrastructure Standard resources, configurations Consolidate to fewer Policy/Value- Based Dynamic optimization to meet SLAs Objective Ability to Change Pricing Scheme Business Interface Resource Utilization Organization IT Management Processes Reduce complexity Economies of scale Flexibility, reduce costs Service- level delivery React Weeks Weeks to days Weeks to minutes Minutes Months to weeks Fixed costs Reduced, fixed costs Fixed shared costs Variable usage costs None, ad hoc Business agility Minutes to seconds Variable business costs Class-of- service SLAs Flexible SLAs End-to-end SLAs No SLAs Known Rationalized Shared pools Service- based pools Unknown Central control Consolidated Pooled ownership Service- oriented None Business SLAs Policy-based sharing Business- oriented Reactive - Proactive Life cycle management Proactive Mature problem mgmt Proactive Prediction, dynamic capacity Service End-to-end service management Chaotic – Reactive Ad hoc Value Policy management SMDS

24. Architecture Design Review 1 Day engagement Follow-up report Limited number

25. Question & Answer Panel

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