Service Oriented Infrastructure a new way of thinking

1
Service Oriented Infrastructurea new way of
thinking

• Kevin Sangwell
• Infrastructure Architect
• Microsoft Regional Head Quarters

2
The Organic Infrastructure

• 5 Separate Web Farms
• 5 Separate SQL Environments
• 5 Separate Identity Stores

3
The Organic Infrastructure

• 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

• Poor user experience
• I have to remember a confusing array of usernames
  passwords
• Infrastructure gaps obvious to me
• 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
• Consolidation doesnt change thinking

6
SOI What it looks like
Services

• Deployment
• Security
• Backup Recovery
• PKI
• DR
• Middleware
• Remote Access
• and more..

7
Services
Consumer
Provider
8
Getting There
9

• 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

10

• Good SOI candidates
• Identity Management / User Directory
• Web Hosting
• Non-Mission Critical Database
• File store

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 Consumer experience

12

• 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
13

• 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 youre defining services in the application
  architecture domain (SOA) you should be doing
  this already.

14

• Low hanging fruit
• Challenges
• QoS many services dont support QoS

Easy
Hard
File, Print
Messaging
Databases
Technology enabled
Process enabled
15

• 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

16
SOI Blockers

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

17
SOI Enablers/facilitators

• Virtualisation is your friend, and your enemy
• Subscriber isolation, easy to add capacity
• doesnt solve all problems remember virtual
  hosts still need managing are lower performance
• Clustering
• Cost of resilience reduces with addition of
  services

18
SOI Enablers/facilitators

• SAN
• Flexibility capacity, replication, backup
• Evaluate on a case-by-case
• Slower than DAS
• Some applications dont support SAN
  replication/backup

19
Example Identity Management Service

• Define Service
• Single directory of users for authentication and
  access control
• Define User Experience
• Transparency (SSO, location independence,
  discoverability)
• Define Consumer Experience (capabilities)
• LDAP Directory (e.g. AD)
• Authentication (LDAP Bind, NTLM, Kerberos)
• Authorisation (Group membership)
• Auditing (directory access)

20
Example Identity Management Service

• Design Logical Service
• Capacity
• Performance
• Scalability
• Backup DR
• Security
• Extensibility for Consumers
• 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 Consumers benefit from these capabilities

23
Does SOI really have an ROI
24
SMDS
Service-Based
Dynamic optimization to meet SLAs
Virtualized
Services managed holistically
Rationalized
Infrastructure resources pooled
Standardized
Consolidate to fewer
Basic
Standard resources, configurations
Uncoordinated infrastructure
25
SOI Enables Role-Based Management
26
Service Levels

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

27
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

28

• Questions?