Architecting Solutions That Span Private and Public Clouds

MICROSOFT CONF IDENT IAL – INTERNAL ONLY

Marc Mercuri Paul SlaterSr. Director ArchitectCloud Strategy EAIP

Architecting solutions that span privateand public clouds

Presented in 2012

SESSION OBJECTIVES AND TAKEAWAYS

Session Objective(s): Discuss the current cloud realities for our customers Introduce Gartner’s “5 Rs”Review common scenarios in the context of the 5 Rs.

Understand the landscape and opportunity for hybridUnderstand the 5 Rs for migration

CustomerNirvana

Host agnosticDeployable in or across cloud(s)Policies determine which cloud(s)Accessible from any deviceManaged via a single pane of glass

Between here + nirvana

Government and industryLegacy applicationsLicensingSymmetryProcesses

Public+private reality

THE REAL WORLD OF ENTERPRISE CUSTOMERS

Self Service ProviderProvider

Ded

icat

edSh

ared

Acce

ss/C

ontro

l

As-Is To-BeTHE SOLUTION ARCHITECTURE PROBLEM

Solution Architectur

e

ServiceModel

ApplicationComponent

IT Deployment Model

ServiceModel

ApplicationComponent

IT Deployment Model

THE ENTERPRISE ARCHITECTURE PROBLEM

ServiceModel

IT Deployment Model

As-Is

ServiceModel

IT Deployment Model

To-Be

Enterprise Architectur

e

WHAT IS THE TO-BE STATE?

PUBLIC + PRIVATE OPPORTUNITIES

Improved Application Capabilities

Accelerated Public Cloud

AdoptionMinimized Costs

Entirely New Classes of

Applications

GettingReady

IdentityNetworkingDataOperationsApplication lifecycle management

DATA FROM SERVICES’ HYBRID CLTCRM

LOB

Exchange

Lync

SharePoint

Storage

HPC

ALM

0

50

100

LicensingIdentity

Global Communication

Security

GRC

Privacy

OperationsIntegration

Portability

Migration/ transition

Data Management

Development process

End user experience

0

50

100

Workloads Scenarios

ApplicationApproaches

Low

High

Like

lihoo

d of

Ado

ptio

n

Activity Definition

Rehost Redeploy the app to a different hardware environment .Only changes are to the hardware infrastructure

Refactor

Make code / configuration changes to connect the app to new infra services Degree of difficulty is based on requisite code changes, which can vary from none to widespread

Revise Modify or extend the existing codebase to support legacy modernization requirements, then use Rehost or Refactor options to deploy to cloud Legacy code must be retained, for which there is frequently no documentation and/or institutional knowledge

Rebuild Rebuild the solution on a provider’s application platform by discarding the existing application code and rearchitecting the application for a new containerLegacy code does not need to be retained

Replace Discard an existing application (or set of applications) and use commercial SaaS

Rehost Refactor Revise Rebuild Replace

Likely to Adopt High Low-Med Low Low-Med High

OPTIONS FOR SOLUTION ARCHITECTSRehost, Refactor, Revise, Rebuild, Replace imply various degrees of difficulty / delivered value

Likelihood of Adoption

x

x

x x

xx

x

x x

x

LIFT AND SHIFT Rehost Refactor Revise Rebuild Replace

PublicOn Premise

Existing application moved “as is” to IaaS,specifically for hosting cost savings.

legacy

BATCH AT SCALE

PublicOn Premise

Batch scripts to process images into multiple sizes and types are run in parallel on multiple IaaS VMs to tackle the one time job with brute force.


IMAGES IN CDN

PublicOn Premise

Website left in its current host and website images moved to blob storage and distributed via Content Delivery Network (CDN)


ADDING ODATA

PublicOn Premise

Existing Java application was moved to the public cloud and extended to provide an Odata feed. The new Odata feed drives their mobile applications.


SHOPPING CART

PublicOn Premise

Moved user-specific shopping cart to table storage and received benefit of faster response times with the ability to have a partition of 1 row


COMPLIANCE

PublicOn Premise

Partner Hosted

Moved travel website to a PaaS environment for cost savings and agility, while moving credit card processing to hosted cloud for PCI compliance.


PARTNER + PAAS

PublicOn Premise

Partner Hosted

Collaboration workload was migrated to a partner hosted cloud and new development to extend it was done with web services and storage in a PaaS environment.


CLOUD OPTIMIZED

PublicOn Premise

Existing application or service is rebuilt to be optimized for cloud – stateless, asynchronous, fault tolerant, highly available, based on standards, etc.


1.0Delphi

2.0C#

OUTSOURCING HR

Partner Hosted

On Premise

An organization replaced their legacy, in house developed HR system to use a SaaS offering from a third party.


Data

ACCESSING ON-PREMISE

PublicOn Premise

Domain joined cloud nodes appear on the local network and access on premise data stores and legacy application data.

Synchronizing sets of data. Sets can be set to synchronize only relevant and allowable data, i.e. exclude PII. In cloud to cloud, user specific data in cloud to device.

PublicOn Premise

SYNCHRONIZING

Non -PII

PII

Non -PII

SCALING

json

PublicOn Premise

On premise data that is frequently accessed is packaged in a file (xml, json), put in blob storage, and made available via CDN.

BIG DATA

Use cloud scale to process big data and make result available to on premise reporting and external devices via services

PublicOn Premise

PublicOn Premise

PULL BACK

Data from a public cloud hosted app is pulled back to on premises. The data is combined with other on prem data stores for analytics and reporting.

SESSION OBJECTIVES AND TAKEAWAYS

Session Objective(s): Discuss the current cloud realities for our customers Introduce Gartner’s “5 Rs”Review common scenarios in the context of the 5 Rs.

Understand the landscape and opportunity for hybridUnderstand the 5 Rs for migration

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Software

Architecting Solutions That Span Private and Public Clouds