1. Service Oriented Infrastructure a new way of thinking
4/23/2019 8:28 AM
Service Oriented Infrastructure a new way of thinking
Kevin Sangwell
Infrastructure Architect
Microsoft Regional Head Quarters
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2. The Organic Infrastructure
4/23/2019 8:28 AM
The Organic Infrastructure
5 Separate Web Farms
5 Separate SQL Environments
5 Separate Identity Stores
ERP
Portal
Financial
Each new application or part of infrastructure is introduced as a stovepipe.
CRM
Document Mgmt
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

3. The Organic Infrastructure
4/23/2019 8:28 AM
The Organic Infrastructure
IT Pain
Separate Identity Stores
Separate and inconsistent Security
Separate Config and Deployment
Separate Resilience/Load Balancing
Separate Monitoring and Management
Portal
ERP
Financial
Higher cost, more complexity
Less secure (no end-to-end identity management)
Compliance difficult/expensive to enforce cross-company
CRM, ERP vendors are typically 3rd party. However these are now being forced to take an SOA perspective.
CRM
Document Mgmt
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

4. The Organic Infrastructure
4/23/2019 8:28 AM
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
Portal
ERP
Financial
Poor user experience re-enforces the “IT as a necessary evil” mindset
Lower productivity
These all increase business risk
Cost implications of diuplication
Poor service experience for customers (inconsistencies)
CRM
Document Mgmt
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

5. Consolidation is the answer, right?
4/23/2019 8:28 AM
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
The problem with consolidation from an SOI perspective is that it is viewed as a project. Once consolidation is complete, its finished. There is no change in approach for future projects, resulting in more stovepipes. SOI fundamentally changes the thinking from stovepipes and solutions to shared services which applications can consume.
The definition of insanity if doing the same thing and expecting different results!
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

6. SOI: What it looks like Deployment Security Backup & Recovery PKI DR
4/23/2019 8:28 AM
SOI: What it looks like
Services
Identity
Management
Deployment
Security
Backup & Recovery
PKI DR
Middleware
Remote Access
and more..
Capabilities
LDAP
Authorisation
Authentication
Audit
Provisioning
De-Provisioning
Federation
Self Service …
Management
& Monitoring
Database
Web Hosting
File
Collaboration
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

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

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

9. Define & prioritise services according to Return on Investment
4/23/2019 8:28 AM
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”
ROI=Estimated cost savings (e.g. lower management overhead) and improved user experience vs technical complexity and scale of service
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

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

11. Define Enterprise Consumer Experience
4/23/2019 8:28 AM
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
User experience is one of the key things which, if done correctly, will make the business think of IT as a strategic asset. The moment IT becomes “exposed” to the business (e.g. having to manually map network drives, call helpdesk to add a new printer when roaming), it becomes an overhead: poor perception, and costs productivity
At this phase, we’re looking at the enterprise user experience, not consuming service experience.
Subscriber experience = graceful failure mode: when service dependency fails, give users a “service currently unavailable” page rather than application error
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

12. Plan Forward Consolidation
4/23/2019 8:28 AM
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
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

13. Plan Forward Consolidation
4/23/2019 8:28 AM
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.
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

14. Low hanging fruit Challenges Plan Backward Consolidation
4/23/2019 8:28 AM
Plan Backward Consolidation
Low hanging fruit
Challenges
QoS: many services don’t support QoS
Easy
Hard
File, Print
Messaging
Databases
Process enabled
Technology enabled
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

15. Transition to Service Management
4/23/2019 8:28 AM
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
Service Support
Incident management
Problem management
Configuration management
Change management
Release management
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

16. SOI Blockers Culture Technology Security Regulatory & compliance
4/23/2019 8:28 AM
SOI Blockers
Culture
Trust between development & infrastructure
Technology
Security
Regulatory & compliance
Aim to centralise these instead of service-orient them
Technology:
no QOS.
Support of vendor (e.g. moving functionality out of stove pipe)
Performance: moving functionality off hosts (e.g. MIIS and SQL)
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

17. SOI Enablers/facilitators
4/23/2019 8:28 AM
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
Virtualisation:
some QOS controls
isolation (security/regulatory)
Clustering:
Offering better SLAs for minimal extra cost
Lowering operational cost – maintenance easier to perform in service hours
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

18. 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

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
Capacity: how much storage? How much network bandwidth
Performance: user/subscriber load
Scalability model: up, out, partition?
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

21. Extensibility Remember “blockers”? Technology (Schema)
4/23/2019 8:28 AM
Extensibility
Remember “blockers”?
Technology (Schema)
Regulatory (Forest)
Security (Account Policies)
Schema: use ADAM as application directory where you can extend the schema. Proxy calls into AD meaning you still take advantage of the directory “service”.
Regulatory: split the users across forests (or maybe domains). Establish trusts if possible.
Security: split the users across domains
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

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. Service-Based SMDS Virtualized Rationalized Standardized Basic
4/23/2019 8:28 AM
Service-Based
SMDS
Virtualized
Dynamic optimization to meet SLAs
Rationalized
Services managed holistically
Standardized
Infrastructure resources pooled
Consolidate to fewer
Basic
Standard resources, configurations
Uncoordinated infrastructure
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
Prediction, dynamic capacity
Service
End-to-end service management
Chaotic – Reactive
Ad hoc
Value
Policy management
Gartner model
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

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?