The process of building new apps or migrating existing apps to a cloud-based platform is complex. There are hundreds of paths you can take and only a few will make sense for you and your business. Get a step-by-step guide on how to plan for a successful app migration.

1. © 2013 Cloud Technology Partners, Inc. / Confidential
1
Migrating the Cloud
A Cookbook for the Enterprise
David S. Linthicum

2. New
Apps
Exis,ng
Apps
Li0
&
Shi0
Par,al
Refactor
Complete
Refactor
Op,mize
Test
Deploy
Operate
&
Monitor
Profile
Architecture
Business
Case
Validate
Select
Define
Develop
Validate
Execute
Data
Security
&
Governance
Metrics
Cloud
PlaLorm

3. New
Apps
Exis,ng
Apps
Profile
Architecture
Business
Case
Validate
Select
Define

4. • Focus
on
exis,ng
applica,ons
• Workload
Profile
• Applica,on
Architecture
• Business
Case
• Applica,on
Valida,on
• Selec,ng
Applica,ons
for
Migra,on
4

5. Why Migrate Applications to Cloud? Investment and Value
2014
2015
2016
Es*mated
Applica*on
Migra*on
Resource
Levels
for
9000
Apps
0
200
400
600
800
1000
1200
FTEs
$0.00
$100,000,000.00
$200,000,000.00
$300,000,000.00
Investment
$0.00
$200,000,000.00
$400,000,000.00
$600,000,000.00
$800,000,000.00
Value

6. Application Architectures Change
Tradi*onal
Applica*on
Architectures
• Scale
Up
• Monolithic
• Stateful
• Infra
Dependent
• Fixed
Capacity
• LAN,
SAN
• Latency
intolerant
• Tightly
coupled
• Consolidated
/
clustered
DB
• Rich
/
chay
client
• Commercial
licenses
• Infra
Supported
Availability
• Manual
build/deploy
• Manual
fault
recovery
• Ac,ve/Passive/DR
• Perimeter
Security
• Allocated
costs
Cloud
Aligned
Applica*on
Architectures
• Scale
Out
• Distributed
• Stateless
• Infra
Agnos,c
• Elas,c
capacity
• WAN,
Loca,on
transparency
• Latency
tolerant
• Loosely
coupled
• Sharded
/
replicated
/
distributed
DB
• Mobile/thin
client
• Cloud
PaaS
/
Open
Source
• App
Supported
Availability
• Automa,on
• Self
healing
• Ac,ve/Ac,ve
• Defense
in
depth
• Metered
cost

7. • Determining
the
right
migra,on
strategy
for
your
app
depends
on
its
level
of
cloud
alignment,
cloud
readiness,
poten,al
benefits
achieved
from
migra,ng,
and
risks
• Not
everything
will
migrate
• Migra,on
strategy
selec,on
also
depends
on
the
target
cloud
endpoint
• Public
and
other
external
cloud
endpoints
may
require
2x-­‐10x
effort
• Rehost
and
replaLorm
strategies
minimize
change
for
applica,ons
that
are
either
cloud
ready,
or
have
higher
risks
or
lower
cloud
benefits
• Refactor
and
reuse
strategies
accept
the
cost
of
change
in
return
for
business
benefits
• There
are
paerns,
processes,
teams
and
tools
to
support
each
strategy
and
each
cloud
endpoint
Application Migration Common Methods and Approaches
• Replace
applica,on
with
SaaS
service
• Build
cloud
na,ve
applica,on
with
similar
/
improved
characteris,cs
and
features
Replace
• Develop
and
produc,ze
common
business
and
technical
services
• Consolidate
similar
applica,ons
and
services
Reuse
• Targeted
changes
to
the
applica,on
to
address
issues
leverage
the
cloud
• Revise
applica,ons
to
leverage
common
services
Refactor
• Move
to
more
cloud-­‐aligned
technology
and
plaLorm
services
• Integra,on
with
cloud
opera,ons
and
monitoring
ReplaLorm
• Li0
and
shi0,
minimizing
changes,
virtualiza,on
replaLorming
• Physical
to
Virtual
to
Cloud
(P2V2C),
Virtual
to
Cloud
(V2C)
Rehost
• Leave
applica,on
as-­‐is;
do
not
move
to
cloud
Retain
• Applica,on
end
of
life
Re,re

8. Application Modernization and Migration Estimates
Lines of
Code
Data Layer Changes
Reqd
SLA Perf Reqs Time People
Very
Simple
< 10,000
1 RDBMS, <
10GB
< 5% 99 Simple <1 week 1
Simple < 100,000
1 RDBMS, <
50GB
< 5% 99 Simple <1 month 2
Moderate < 500,000
1 Replica, <1
TB
< 10% 99.9 Moderate < 6 months 5
Complex < 2,000,000
Active-Active,
< 1PB
< 20% 99.95 High < 24 months 20
Very
Complex
> 2,000,000 Global, PBs > 20% > 99.95 High > 24 months 50
Notes:
1) Assumes
liF
and
shiF
objec*ves
or
minor
(<20%)
refactoring.
2) Assumes
applica*on
is
<8
years
old
or
has
not
undergone
major
tech
refresh
within
last
8
years.
If
not,
add
age
tax
of
50%
for
each
8
year
mul*ple.
3) Addi*onal
effort
required
for
applica*ons
with
*ght
integra*on
or
mul*ple
integra*on
points.
4) Data
refactoring,
migra*on,
or
implementa*on
of
data
services
could
double
the
es*mate.
5) Assumes
ordinary
security,
audit,
legal,
and
compliance
requirements.
6) Assumes
use
of
cTP
IP
(eg
ADF,
PaaSLane)
7) Assumes
1:3
Onsite:Offshore
8) Assumes
Senior
level
Architects
Complexity Duration Architects Notes
Breadth Analysis Moderate 1 Day 1
1 experienced architects analyze 80
applications/month on average
Depth Analysis
(Modernization)
Moderate 10 Days 2
2 architect team can perform detailed
migration analysis for 2 applications/month
on average

9. Li0
&
Shi0
Par,al
Refactor
Complete
Refactor
Test
Develop
Data
Security
&
Governance
Cloud
PlaLorm

10. • Op,ons
• Cloud
Na,ve
• Dealing
with
the
Data
• Applica,on
Security
• Applica,on
Governance
– The
ability
to
govern
cloud
microservices
– The
ability
to
govern
cloud
orchestra,ons
– The
ability
to
govern
resources
• How
to
Approach
Tes,ng
• Selec,ng
the
Cloud
PlaLorm
• Selec,ng
the
Development
PlaLorm
10

11. Achieving Cloud-Native Application Architecture
Tradi*onal
Applica*on
Architectures
• Scale
Up
• Monolithic
• Stateful
• Infra
Dependent
• Fixed
Capacity
• LAN,
SAN
• Latency
intolerant
• Tightly
coupled
• Consolidated
/
clustered
DB
• Rich
/
chay
client
• Commercial
licenses
• Infra
Supported
Availability
• Manual
build/deploy
• Manual
fault
recovery
• Ac,ve/Passive/DR
• Perimeter
Security
• Allocated
costs
The
“Old
World”
Cloud
Aligned
Applica*on
Architectures
• Scale
Out
• Distributed
• Stateless
• Infra
Agnos,c
• Elas,c
capacity
• WAN,
Loca,on
transparency
• Latency
tolerant
• Loosely
coupled
• Sharded
/
replicated
/
distributed
DB
• Mobile/thin
client
• Cloud
PaaS
/
Open
Source
• App
Supported
Availability
• Automa,on
• Self
healing
• Ac,ve/Ac,ve
• Defense
in
depth
• Metered
cost
The
“New
World”
The
Targets
Refactor
Con,nuous
Delivery

12. Cloud Application Maturity

13. Agile
Application
Migration
• Agile
refactoring
and
tes,ng
sprints
• Kanban
DevOps
infrastructure
sprints
• Cloud
SDLC
environments
• Con,nuous
Integra,on
• Deployment
automa,on
• Data
migra,on
and
mgmt
implementa,on
• Monitoring
and
Ops
management
integra,on
Migration
Planning
• App
and
architecture
refactoring
strategy
• Code
refactoring
stories
• App
replaLorming
and
opera,ons
integra,on
plan
• Cloud
services
mapping
and
DevOps
stories
• Build/test/deploy
plan
• Cost,
,me,
resources
and
effort
plan
Depth
• Cloud
readiness
assessment
• PlaLorm
config
analysis
• Key
metrics:
scalability,
performance,
security
• Migra,on
effort
es,ma,on
• Code
remedia,on
recommenda,ons
Breadth
• Applica,on
porLolio
classifica,on
• Target
endpoint
analysis
• Applica,on
to
endpoint
mapping
Application Portfolio Application

14. Continuous Delivery with CI, DevOps and the Cloud
DevOps
Automated
Provisioning
Automated
Tes,ng
Automated
Build
&
Deploy
SCM/Version
Build
Scripts
Dependency
Map
Component
Deploy
System
Deploy
Test
Scripts
Test
Deploy
Load
/
Soak
Scripts
Data
Provisioning
Baseline/Benchmark
Tes*ng
Reports
Image
Management
Patch
Management
Auto
Env
Deploy
Start/Stop
Scripts
Rolling
Upgrades
Security
Config
Integrated
Deploy
and
Test
DevOps
should
really
be
called
DevTestOps
• Collabora,on
and
shared
tools
on
the
Dev,
QA
and
Infra
automa,on
teams
• Capture
every
request
–
no
ad-­‐hoc
work
or
changes
• Agile
Kanban
project
management
for
automa,on
and
DevOps
requests
• Log
metrics
on
both
manual
and
automated
processes
• Test
automa,on
and
test
data
provisioning
for
infrastructure
as
well
as
applica,ons
• Acceptance
tests
for
each
deployment:
infrastructure,
applica,on,
test
suite
• Con,nuous
feedback
between
the
teams
to
spot
gaps,
issues
and
inefficiencies
Automa5on:
It’s
All
Code
• Save
it
• Version
it
• Measure
it
• Evolve
it
Con*nuous
Feedback
DevOps Best Practices

15. IAM
Is
Key

17. 17

18. Picking
Clouds
18

19. Op,mize
Validate
Security
&
Governance
Metrics
Cloud
PlaLorm

20. • Op,mize
and
Test
• Performance
• Stability
• Fit-­‐to-­‐use
• Gathering
Metrics
20

21. 21
Source:
Cisco

22. 22

23. Deploy
Operate
&
Monitor
Execute
Security
&
Governance
Metrics
Cloud
PlaLorm

24. Moving
to
Produc,on
• Applica/on
deployment,
or
hos,ng
the
applica,on
on
the
public
cloud.
• Applica/on
0pera/ons,
the
processes
required
to
operate
the
new
or
migrated
applica,on.
• Applica/on
monitoring
means
that
we
monitor
the
various
applica,on
components
to
determine
the
current,
past,
and
even
the
future
health
of
the
cloud-­‐based
applica,on.
24

25. Q&A
25

26. Thank
You
26

27. Mobility At New Relic!
Abner Germanow Senior Director, Solutions Marketing @AbnerG!

28. ©2008-15 New Relic, Inc. All rights reserved.
The New Cloud Software Team
2
Enable
Developers
• AWS won start-ups
• AWS, Google, HP, IBM, Microsoft,
Pivotal, and more are investing $B
to woo software teams
• New Model: Adopt and then buy
Migrate
Existing Apps
• Reduce legacy costs
• Re-architect key apps
• Services: Reduce risk, then
transform business
Experiment To
Transform
• Agility = Constant Change
• Data driven software
development

29. ©2008-15 New Relic, Inc. All rights reserved.
Relational Data
App Server
Customer
Web Server
Browser
3
Mobile / Apps / Browser
Public Cloud
NoSQL data store
Private Cloud
API
Micro Services
Private Cloud
Application Data
Business Data
Customer Experience Data
Managing Software has become
a Big Data Analytics Problem
Ops/Developer Career Success:
Application performance must be measured
in the context of customer experience & business success

30. ©2008-15 New Relic, Inc. All rights reserved.
Accountability In The Cloud
Business
Success
Application
Performance
Customer
Experience
How are customers engaging?
Am I open for business?
How is my business doing?
4
Amazon
Accountability
Customer
Accountability

31. Cloud Migration
How does New Relic help?

32. Old Assumption
New Assumption
New Assumption
If the server is working,
the application is fine
Application behavior first and
infrastructure behavior second

33. Data
Data
New Relic: Put Your Apps Wherever You Want
Customer
Mobile / Apps / Browser
Data

34. New Relic Helps Reduce Migration Risks
Performance Post Migration
& During Optimization
Pre-migration Feasibility &
Benchmarking

35. For the Ops teams
Migration often goes hand in hand with increased automation
What’s in your ops stack?
ALL the deployment tools:
All the alerting tools:
Ticketing & Service Management:
Deploy Agents with YOUR
Automation Tools
Monitor Your Cloud Servers For
Free
Integrate with YOUR workflow

36. High
Expectations
Blame
Game
Intensity
Rises
The problem
must be the
cloud’s fault
Pressure to
declare victory
on multiple
fronts
The Politics of Migration
Show me the
new apps!!?
Performance gains?
Cost controls?
Optimize costs?
Report on spikes
More?
Where is the money!!?

37. What Should You Buy?
Step 1: Migration Success
Land: Assess & Migrate
Reduce Risk
App Performance
Step 2: Software Success
Expand: Customer experience
Build Competitive Weapons
Customer Experience
Business Success

38. Why Is New Relic Unique In Cloud Migration?
Cloud Leadership
Cloud Flexibility
Thousands of
customers monitor
their apps in Amazon’s
cloud.
Cover your XaaS!!!
Reduce risk -> Build
Competitive Weapons
Platform

39. What’s our New Relic Perspective?
Start Small And Expand – Focus On Development Cycles And Scaling
Re-Fit
Re-Architect / Modernize
Lift & Shift
WHY??
Medium Risk, High Reward
Auto-scaling can produce
savings & improve experience
Good place to start, build
cloud skills
High Risk, High Reward
Devops / fast cycle times
required.
SaaS economies of scale
and code consistency
drives innovation.

40. Next Steps
See a demo
Try it out
Get quick results

41. Other Resources
In the follow-up email…
• Link to the webinar recording
• Cloud Migration Cookbook
Cloud Migration Resources
http://newrelic.com/solutions/cloud-migration
Monitoring Hybrid Applications
http://newrelic.com/hybrid-cloud-monitoring