Service Oriented Infrastructure a new way of thinking

Service Oriented Infrastructure a new way of thinking Kevin Sangwell Infrastructure Architect Microsoft Regional Head Quarters

The Organic Infrastructure ERP • 5 Separate Web Farms • 5 Separate SQL Environments • 5 Separate Identity Stores. Portal Financial CRM Document Mgmt

The Organic Infrastructure • IT Pain – Separate ERP – Separate CRM Identity Stores Portal and inconsistent Security Config and Deployment Financial Resilience/Load Balancing Monitoring and Management Document Mgmt

The Organic Infrastructure • Poor user experience – I have to remember a confusing Portal array of ERP usernames & passwords – Infrastructure gaps obvious to me Financial – My information is different across systems Document – CRM It takes weeks for me to get access Mgmt to everything I need – Stuff is slow

Consolidation is the answer, right? • Reduces number of stove pipes, but doesn’t solve them • Next application/project adds another stovepipe • I think of this as “backwards consolidation” • Consolidation doesn’t change thinking

SOI: What it looks like Services Identity Management & Monitoring Database Web Hosting File Email Collaboration • • • – Deployment Capabilities –LDAP Security Authorisation –Authentication Backup & Recovery Audit Provisioning –De-Provisioning PKI Federation Service –Self. DR … – Middleware – Remote Access – and more. .

Services Identity Management CRM Management & Monitoring Database Web Hosting Portal File Email Collaboration Provider Consumer

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

Define & Prioritise Services • Define & prioritise services according to Return on Investment • Put low hanging fruit at the top • The difference between centralised and service-oriented is “shared service”

Define & Prioritise Services • Good SOI candidates – Identity Management / User Directory – Web Hosting – Non-Mission Critical Database – File store

Define Enterprise Consumer Experience • 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 Consumer experience

Plan Forward Consolidation • Forward consolidation for each service – Attach to Projects Project 1 Project 2 Web Hosting Requirements Additional Hosting Requirements New Web Farm as a service Increase capacity

Plan Forward Consolidation • The future is difficult to predict - what i/o, RAM, CPU will my future application need? • Abstract & Standardise – Categorise subscribers as High, Medium or Low for • • • Capacity (storage & bandwidth) Load (concurrency / transactions) Performance (responsiveness / user expectations) Availability Result: easier to accommodate new consumers and plan capacity. – Implement standard platform (hardware/software) for each of above – When you’re defining services in the application architecture domain (SOA) you should be doing this already.

Plan Backward Consolidation • Low hanging fruit Easy File, Print Process enabled Hard Messaging Databases Technology enabled • Challenges – Qo. S: many services don’t support Qo. S

Transition to Service Management • Assign Service Manager for each service – Owns relationship with other services • Consumers • Providers (inbound dependencies) – Service Delivery • • • Service Level Management Capacity Management Availability Management IT Continuity Management Financial Management – Service Support

SOI Blockers • Culture – Trust between development & infrastructure • Technology • Security • Regulatory & compliance – Aim to centralise these instead of service-orient them

SOI Enablers/facilitators • Virtualisation is your friend, and your enemy – Subscriber isolation, easy to add capacity – doesn’t solve all problems: remember virtual hosts still need managing & are lower performance • Clustering – Cost of resilience reduces with addition of services

SOI Enablers/facilitators • SAN – Flexibility; capacity, replication, backup – Evaluate on a case-by-case • Slower than DAS • Some applications don’t support SAN replication/backup

Example: Identity Management Service 1. Define Service – “Single directory of users for authentication and access control” 2. Define User Experience – Transparency (SSO, location independence, discoverability) 3. Define Consumer Experience (capabilities) – – LDAP Directory (e. g. AD) Authentication (LDAP Bind, NTLM, Kerberos) Authorisation (Group membership) Auditing (directory access)

Example: Identity Management Service 4. Design Logical Service – – – Capacity Performance Scalability Backup & DR Security Extensibility for Consumers 5. Design Physical Service – – Server sizes Server locations

Extensibility • Remember “blockers”? – Technology (Schema) – Regulatory (Forest) – Security (Account Policies)

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

Does SOI really have an ROI

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

SOI Enables Role-Based Management

Service Levels • IT Cost Transparency • Business can choose service based on business needs and cost • IT more closely aligned with the business

Summary • SOI is a change of thinking • SOI is dependent on Service Management • Will result in fewer servers, and better availability/management • Enables role-based management • SOI is should be adopted gradually

• Questions?