• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Service Oriented Infrastructure
 

Service Oriented Infrastructure

on

  • 813 views

Infraestructura

Infraestructura

Statistics

Views

Total Views
813
Views on SlideShare
805
Embed Views
8

Actions

Likes
1
Downloads
16
Comments
0

2 Embeds 8

http://www.linkedin.com 6
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Each new application or part of infrastructure is introduced as a stovepipe.
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Higher cost, more complexity Less secure (no end-to-end identity management) Compliance difficult/expensive to enforce cross-company CRM, ERP vendors are typically 3 rd party. However these are now being forced to take an SOA perspective.
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 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)
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 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!
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. ROI=Estimated cost savings (e.g. lower management overhead) and improved user experience vs technical complexity and scale of service
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 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 service user experience. Subscriber experience = graceful failure mode: when service dependency fails, give users a “service currently unavailable” page rather than application error
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Infrastructure Architects can help Solution Architects in this area
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Service Support Incident management Problem management Configuration management Change management Release management
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Technology: no QOS. Support of vendor (e.g. moving functionality out of stove pipe) Performance: moving functionality off hosts (e.g. MIIS and SQL)
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 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
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Capacity: how much storage? How much network bandwidth Performance: user/subscriber load Scalability model: up, out, partition?
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 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
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Gartner model
  • 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Service Oriented Infrastructure Service Oriented Infrastructure Presentation Transcript

  • Rethinking Infrastructure Architecture: Service Oriented Infrastructure
    • Kevin Sangwell
    • Infrastructure Architect
    • Microsoft EMEA HQ
  • The Organic Infrastructure
    • 5 Separate Web Farms
    • 5 Separate SQL Environments
    • 5 Separate Identity Stores
    CRM ERP Financial Portal Document Mgmt
  • The Organic Infrastructure
    • IT Pain
      • Separate Identity Stores
      • Separate and inconsistent Security
      • Separate Config and Deployment
      • Separate Resilience/Load Balancing
      • Separate Monitoring and Management
    CRM ERP Financial Portal Document Mgmt
  • The Organic Infrastructure
    • 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
    CRM ERP Financial Portal Document Mgmt
  • 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”
    • Doesn’t change thinking
  • SOI: What it looks like Services
      • Deployment
      • Security
      • Backup & Recovery
      • PKI
      • DR
      • Middleware
      • Remote Access
      • and more..
    Identity Management Management & Monitoring Database File Email Collaboration Web Hosting LDAP Authn Authz Audit Provisioning De-Provisioning Federation Self Service …
  • SOI: What it looks like Services Subscribers Publishers Identity Management Management & Monitoring Database File Email Collaboration Web Hosting CRM Portal
  • Getting There Define & Prioritise Services Define Enterprise Consumer Experience Plan Forward & Backward Consolidation Transition to Service Management
    • 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
    • Good candidates
      • Identity Management / Directory
      • Web Hosting
      • Database
      • File store
    Define & Prioritise Services
    • 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 Enterprise Consumer Experience
    • Forward consolidation for each service
      • Attach to Projects
      • Major pain/cost areas such as IDM
    Project 1 Web Hosting Requirements New Web Farm as a service Project 2 Additional Hosting Requirements Increase capacity Plan Forward Consolidation
  • 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 you’re defining services in the application architecture domain (SOA) you should be doing this already.
    • Backward consolidation
      • Low hanging fruit
    • Challenges
      • QOS: many services don’t support QOS
    File, Print Messaging Databases Easy Hard Technology enabled Process enabled Plan Backward Consolidation
    • Assign Service Manager for each service
      • Owns relationship with other services
        • Subscribers
        • Publisher
      • Service Delivery
        • Service Level Management
        • Capacity Management
        • Availability Management
        • IT Continuity Management
        • Financial Management
      • Service Support
    Transition to Service Management
  • Blockers
    • Technology
    • Security
    • Regulatory & compliance
      • Aim to centralise these instead of service-orient them
  • SOI Enablers/facilitators
    • Virtualisation is your friend, and your enemy
      • But doesn’t 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 don’t support SAN replication/backup
  • 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
    • Don’t 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
  • 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)
  • Example: Identity and Access Management
    • Design Logical Service
      • Capacity
      • Performance
      • Scalability
      • Backup & DR
      • Security
      • Extensibility for subscribers
    • 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 subscribers benefit from these capabilities
  • 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 SMDS 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 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
  • Architecture Design Review
    • 1 Day engagement
    • Follow-up report
    • Limited number
    • Question & Answer Panel
  • © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.