Keeping an application running at scale in the cloud is fundamentally different than keeping your applications running in your own data centers. Cloud technologies are different, the way you scale is different, the way you troubleshoot is different, and the monitoring you need is different. From static compute to dynamic autoscaling to serverless services and microservices, combined with the demands of creating new digital businesses, cloud services provide new opportunities and challenges. In this session, New Relic’s Lee Atchison and Morningstar, a global investment research company, will discuss the differences in cloud technologies impact on monitoring and architectural strategies when migrating and scaling applications on AWS.  This session is brought to you by AWS Summit Chicago sponsor, New Relic.

1. © 2017, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Lee Atchison ∙ Senior Director Strategic Architecture
New Relic, Inc.
Migrating with Morningstar:
The Path to Dynamic Cloud
Keeping Your Application Running… at Scale
leeatchison@leeatchison

2. Does this sound familiar…

6. You had power
most of the time.
Why are you
complaining?

7. I Hope, I Hope, I Hope
the Site Stays Up

8. Keeping Your App Running… at Scale
8
Availability…
… is more than
you think it is.

9. Does this sound like something you’ve heard recently…
… overheard OPs conversation...

10. The Conversation…
“We were wondering how
changing a setting on our
MySQL database might
impact our performance…

11. The Conversation…
“We were wondering how
changing a setting on our
MySQL database might
impact our performance…
… but we were worried
that the change may
cause our production
database to fail…”

12. The “Scary” Overheard Conversation…
“… Since we didn’t want to bring
down production, we decided to
make the change to our backup
(replica) database instead…
Under
Construction
… but we were worried
that the change may
cause our production
database to fail…”

13. The “Scary” Overheard Conversation…
“… Since we didn’t want to bring
down production, we decided to
make the change to our backup
(replica) database instead…
… After all, it wasn’t
being used for anything
at the moment.”
Under
Construction

14. The “Scary” Overheard Conversation…
Until, of course, the backup was needed…
Under
Construction
X

15. The “Scary” Overheard Conversation…
Until, of course, the backup was needed…
This is a true story
Under
Construction!!!!X
X

16. Availability can be more subtle, for example…

17. 17
300ms
1.5s
17

18. 18
18
.9s

19. 19
19

20. 20
The Data from Monitoring Your App
Dwarfs the Data Inside the App

21. 21
User Experience
Business Outcome
Servers
Apps
Big Data Problem

22. High
Expectations
Blame
Game
Intensity
Rises
The problem
must be
someone
else’s fault
Panic

23. What happened?

24. Need Data at Every Level
Amazon EC2 Instance
BrowserMobile
Server (Virtual)
Hardware
Server OS
Application &
Application
Microservices
Typical Server / Amazon Elastic
Compute Cloud (Amazon EC2) Instance
• Application & Application
Microservices
• Server OS
• Hardware (virtual)

25. Amazon EC2 Instance
BrowserMobile
Server (Virtual)
Hardware
Server OS
Application &
Application
Microservices
Low Level Monitoring
Amazon
CloudWatch
AWS
CONSOLE
Amazon CloudWatch
Monitors
• Amazon EC2 instance
• Virtualization
• Hardware
• [CPU / Disk / Networking]
Doesn’t Monitor:
• Server OS
• Memory / Filesystem
• Processes
• Configuration
• Application
- Latency
- Error rates

26. Amazon EC2 Instance
BrowserMobile
Server (Virtual)
Hardware
Server OS
Application &
Application
Microservices
DASHBOARDS
Infrastructure / Application Monitoring
New Relic
Application
Monitoring
New Relic
Infrastructure
Monitoring
Amazon
CloudWatch
AWS
CONSOLE
Monitors (Server):
• How O.S. is performing
• Configuration Changes
• Processes
• Hardware
Monitors (Application):
• App health
• App performance
• Microservices
Doesn’t Monitor:
• Virtualization

27. Amazon EC2 Instance
BrowserMobile
Server (Virtual)
Hardware
Server OS
Application &
Application
Microservices
Full Stack Monitoring
New Relic
Application
Monitoring
New Relic
Infrastructure
Monitoring
Amazon
CloudWatch
AWS
CONSOLE
Integrations
New Relic
Monitors
AWS
monitors
DASHBOARDS
Amazon CloudWatch
• Visibility into virtualization
• CPU / Disk / Networking
• 14 AWS Services
APM
• CPU / Disk / Networking
• Memory / File System
• Processes
- Infrastructure components
- Configuration inventory
• Application / Microservices:
- Latency
- Error rates
- App insights

28. Why Measurement Matters
2

29. Success in Software Analytics
29
Confidential ©2008-15 New Relic, Inc. All rights reserved.
Application
Performance
Customer
Experience
Business
Outcome

31. Keeping Your App Running… at Scale
3
Availability…
… is more than
you think it is.
Dynamic
Cloud…
... make availability
happen.

32. The Cloud Can Help
How do we use the cloud to accomplish this?
Better Data Center Dynamic Environment

33. Better Data Center
Dynamic EnvironmentBetter Data Center

34. Cloud as a “Better Data Center”
Resources are
allocated to uses, just
like in a data center
Provisioning
process
is faster
Lifetime of
components is
relatively long
Capacity planning is
still important and
still applies

35. Why Use a “Better Data Center”?
Add New Capacity
(Faster)
Improve Application Availability
(Redundancy)
Compliance

36. Dynamic Cloud
Better Data Center Dynamic Environment

37. Cloud as a “Dynamic Tool for Dynamic Apps”
Use only the
resources you need
Allocate / de-allocate
resources on the fly
Resource allocation is
an integral part of your
application architecture

38. Dynamic Cloud
Resources are: Application in charge:
Allocated Application is aware of and is
controlling traditional OPs resources
Consumed De-allocated

39. Dynamic Usage Example…
Docker Container Age
(Count vs. Hours)
1 Hour
200 days 833 days

40. Dynamic Usage Example…
Docker Container Age
(by minute and hour)
1,200,000
11% under one minute
Container age (minutes)

41. Dynamic Cloud Technologies
Dynamic Cloud is about scaling and availability
Amazon EC2
Auto Scaling
Mobile / IoT Dynamic routing
Load balancing
Queues and notifications
Docker

42. Dynamic Cloud Enables Better Applications Faster
Traditional
Data Center
Cloud
Data Center
Dynamic
Cloud
Good Better Best
The way you’ve done things in the past
won’t work in the future.

43. Dynamic Cloud
Server running
application / processes
Process running
a command
Function performing
a task or operation
Amazon EC2 Docker AWS Lambda
Things happen faster because of…

44. Microcomputing & AWS Lambda
Also known as:
• Functions as a
Service (FaaS)
• Compute as a
Service (CaaS)
• Serverless
• Highly dynamic
• Incredibly scalable
• No infrastructure to
provision
• Massively shared
infrastructure

45. AWS Lambda
Amazon S3
Bucket
Amazon
DynamoDB
Amazon API
Gateway
Amazon SQS
RESOURCESSOME
Amazon S3
Bucket
Amazon API
Gateway Amazon SQS
RESOURCESSOME
AWS Lambda
Execution
AWS Lambda
Scripts
• Takes an event from an AWS
resource (a trigger)
• Creates an instance
to execute
• Can impact original or
different AWS resource
• Any number of instances can
run at a time

46. Dynamic Cloud
Higher Availability
Dynamic Cloud
Easier Scaling
Faster Change
Faster Response

47. Dynamic cloud has unique monitoring requirements…
How do I track what the dynamic
cloud is doing for me (or to me)?

48. What Is a Dynamic Cloud Application?
• Application & Application Microservices
Responsible for the parts you care about
• Infrastructure
• Allocation/Provisioning
• Scaling
Let cloud manage the rest
Server OS
Server (Virtual)
Hardware
Application &
Application
Microservices
Provisioning
Application &
Application
Microservices
Application &
Application
Microservices
BrowserMobile

49. Server OS
Server (Virtual)
Hardware
Application &
Application
Microservices
Provisioning
Application &
Application
Microservices
Application &
Application
Microservices
BrowserMobile
Monitoring Dynamic Cloud Applications
AWS
CONSOLE
Amazon
CloudWatch

50. Server OS
Server (Virtual)
Hardware
Application &
Application
Microservices
Provisioning
Application &
Application
Microservices
Application &
Application
Microservices
BrowserMobile
AWS InfrastructureApplication Performance
AWS
CONSOLE
New Relic
Application
Monitoring
New Relic
Infrastructure
Monitoring
DASHBOARDS
Integrations
Amazon
CloudWatch

51. Server OS
Server (Virtual)
Hardware
Application &
Application
Microservices
Provisioning
Application &
Application
Microservices
Application &
Application
Microservices
BrowserMobile
AWS
CONSOLE
New Relic
Application
Monitoring
New Relic
Infrastructure
Monitoring
DASHBOARDS
AWS InfrastructureApplication Performance
New Relic
Monitors
AWS monitors
Integrations
Amazon
CloudWatch

52. Server OS
Server (Virtual)
Hardware
Application &
Application
Microservices
Provisioning
Application &
Application
Microservices
Application &
Application
Microservices
BrowserMobile
How do you monitor this?
?How do you
monitor this?

53. Where did it go? It was just here!!
The thing you monitored 10 minutes ago…
... doesn’t exist anymore!?

54. Monitoring the Dynamic Cloud
Monitor the Cloud
Components themselves
Monitor the lifecycle of
the Cloud Components
Very different than monitoring traditional Data Center components

55. Changing World
Ops
Previous – STATIC World

56. Changing World
Dev
Now – DYNAMIC World
Ops
Ops
Previous – STATIC World

57. Changing World
Ops
We know
• Change is inevitable
We must
• Embrace and drive change
Enabling
• Quicker growth
• More reliable growth
Dev
Now – DYNAMIC World

58. Keeping Your App Running… at Scale
5
Dynamic
Cloud…
... make availability
happen.
Migration…
... how do I get my
app to the cloud?

59. High
Expectations
Blame
Game
Intensity
Rises
“The
problem
must be the
cloud’s fault”
Pressure to
declare victory
in the migration
The Politics of Migration
Show me the
new apps!!?
Promised
Performance gains?
Cost controls?
Optimize costs?
Why is it taking so long?
Migration failure…

60. Ops
Use the Cloud
• Move in a controlled way
• Learn as you go
• Measure everything
Does Not Have to Be Painful…

61. Experiment
Secure the Cloud
Enable Servers, Enable SaaS
Enable Value-Added Services
Enable Unique Services
Mandate Cloud Usage
Standard steps
most companies
follow
Progressions in Cloud Adoption…
The Controlled Way

62. Experiment
Progressions in Cloud Adoption…
The Controlled Way

63. Progressions in
Cloud Adoption
What is this cloud thing?
Enterprise IT Cloud Adoption Strategy
Experiment
• Non-evasive, safe technologies
• Amazon Simple Storage Service (Amazon S3)
• Perhaps: Amazon CloudFront, Amazon Simple
Queue Service (Amazon SQS), Amazon
Simple Email Service (Amazon SES)
• Tend to stay away from cloud servers (Amazon
EC2)
• Security: Easy as one-offs
• No “policies” implemented yet
• “Just seeing what this is all about”

64. Experiment
Secure the Cloud
Progressions in Cloud Adoption…
The Controlled Way

65. Enterprise IT Cloud Adoption Strategy
Secure the Cloud
• AWS Identity Access and Management (IAM)
(Credentials)
• Amazon Virtual Private Cloud (Amazon VPC)
(Secure network)
• AWS Direct Connect (just another data center)
• Cloud policies begin to be formed
• All parts of the company are now involved
• Critical evolution point
Can we trust the cloud?
Progressions in
Cloud Adoption

66. Experiment
Secure the Cloud
Enable Servers, Enable SaaS
Progressions in Cloud Adoption…
The Controlled Way

67. Enterprise IT Cloud Adoption Strategy
Enable Servers, Enable SaaS
• Amazon EC2
• Basic “data center migration”
• Just another server type available…
• Multiple AZs/Regions
• Part of multi–data center resiliency strategy
• Independently: SaaS usage increases
• Non-critical or internal uses first
The cloud seems to work pretty well…
Progressions in
Cloud Adoption

68. Experiment
Secure the Cloud
Enable Servers, Enable SaaS
Enable Value-Added Services
Progressions in Cloud Adoption…
The Controlled Way

69. Enterprise IT Cloud Adoption Strategy
Enable Value-Added Services
• Managed Databases
• Amazon Relational Database Service
(Amazon RDS)
• Amazon Aurora
• Other Managed Services
• AWS Elastic Beanstalk, Amazon SES,
Amazon SQS
• Amazon Elasticsearch Service
Dynamic Cloud becomes a thing…
Progressions in
Cloud Adoption

70. Experiment
Secure the Cloud
Enable Servers, Enable SaaS
Enable Value-Added Services
Enable Unique Services
Progressions in Cloud Adoption…
The Controlled Way

71. Enterprise IT Cloud Adoption Strategy
Enable Unique Services
• High value, Cloud-specific services
• AWS Lambda, Amazon Kinesis
• Amazon DynamoDB
• Amazon Simple Workflow Service (Amazon SWF),
Amazon Elastic Transcoder
• Amazon Redshift
• Point of commitment...
...dependent on cloud
Dynamic Cloud is deeply ingrained…
Progressions in
Cloud Adoption

72. Experiment
Secure the Cloud
Enable Servers, Enable SaaS
Enable Value-Added Services
Enable Unique Services
Mandate Cloud Usage
Progressions in Cloud Adoption…
The Controlled Way

73. Enterprise IT Cloud Adoption Strategy
Mandate Cloud Usage
• Cloud as a data center replacement
• Company is now “all in” with cloud
• Netflix…
Why do we need our own data centers?
Progressions in
Cloud Adoption

74. Experiment
Secure the Cloud
Enable Servers, Enable SaaS
Enable Value-Added Services
Enable Unique Services
Mandate Cloud Usage
The Steps Aren’t Easy…

75. Experiment
Secure the Cloud
Enable Servers, Enable SaaS
Enable Value-Added Services
Enable Unique Services
Mandate Cloud Usage
Progressions in Cloud Adoption
Different Companies
Different Speeds
Different Needs

76. Cloud Adoption Strategies
Application
Cloud Adoption Strategy
• Experiment/Peripheral Usage
• Cloud Servers
• Managed Components
• Unique Components
• Application Cloud Committed
Enterprise IT
Cloud Adoption Strategy
• Experiment
• Secure the Cloud
• Enable Servers, Enable SaaS
• Enable Value-Added Services
• Enable Unique Services
• Mandate Cloud Usage

77. Application
Adoption
Corporate
Adoption
Cloud Adoption
Mandate
Committed
Allow Value-Added
Allow SaaS
Allow Servers
Secure
Experiment
Experiment Servers Managed
Components
Unique
Components
Committed
Critical
Applications
New
Applications
Non-Critical/
Internal
Applications
Step #1
Step #2
Step #4
First Steps
Application
Rewrites
Step #3

78. IAM
Amazon VPC
Non-Integral
SaaS
Amazon EC2
Integral
SaaS
Amazon RDS
Amazon SES
AWS Lambda
Amazon Kinesis
Application
Adoption
Corporate
Adoption
Mandate
Committed
Allow Value-Added
Allow SaaS
Allow Servers
Secure
Experiment
Experiment Servers Managed
Components
Unique
Components
Committed
Critical
Applications
New
Applications
Non-Critical/
Internal
Applications
Step #1
Step #2
Step #4
First Steps
Application
Re-Writes
Step #3
Amazon S3
Cloud Adoption

79. Adoption
Sweet Spot
First Steps
Application
Adoption
Corporate
Adoption
Mandate
Committed
Allow Value-Added
Allow SaaS
Allow Servers
Secure
Experiment
Experiment Servers Managed
Components
Unique
Components
Committed
Cloud Adoption
Center of Gravity

80. Integral
SaaS
Amazon RDS
Amazon SES
AWS Lambda
Amazon Kinesis
Application
Adoption
Corporate
Adoption
Mandate
Committed
Allow Value-Added
Allow SaaS
Allow Servers
Secure
Experiment
Experiment Servers Managed
Components
Unique
Components
Committed
Amazon
S3
Amazon EC2
Cloud Adoption
Center of GravityIAM
Amazon VPC
Non-Integral
SaaS
Adoption
Sweet Spot

81. Migrating to the Cloud…
How can I be successful?

82. Adoption Success Strategies
Understand
where your
culture is
Consciously
plan your
acceptance
Drive your
cultural change
to your
desired level
Monitor
your adoption
Understand
your needs

83. Monitor Your Adoption
Before Migration
Baseline application
(servers, databases,
caches, applications,
microservices)
Determine your steady
state

84. Monitor Your Adoption
During Migration
Incorporate cloud’s
internal monitoring
Continue
application
monitoring
Understand and solve all deviations from steady state…

85. The Biggest Role Monitoring Plays in Migration
Performance Post-Migration
& During Optimization
Pre-Migration Feasibility &
Benchmarking

86. Continue Monitoring…
Infrastructure is
now out of your
control
Some cloud specific
concerns (Amazon EC2
instance failures,
instance degradation)
Dynamic Technologies
Impact Our Applications
Understand
application
impact
Ongoing
application &
infrastructure
monitoring is
essential
Monitor Your Adoption

87. Keeping Your App Running… at Scale
Dynamic
Cloud…
... make availability
happen.
Migration…
... how do I get my
app to the cloud?
Availability…
… is more than
you think it is.
Monitor your application and infrastructure

88. Monitoring Just the Server
Amazon EC2 Instance
Server OS
Server (Virtual)
Hardware
Application &
Application Microservices
AWS
CONSOLE Amazon
CloudWatch
Worked when rate of change was low…

89. Dynamic World
Dev
Now – DYNAMIC World
Ops

91. Panic

92. Change is Speeding Up
Dynamic Cloud enables better applications faster
Traditional
Data Center
Cloud
Data Center
Dynamic
Cloud
Good Better Best
The way you’ve done things in the past
won’t work in the future.

93. Financial Services
North America
Unified view of Information
across hybrid cloud
Elastic scalability to support
spikes in demand
Baseline metrics support
AWS migration success
“New Relic allows us to build a solid foundation for all
of our next-gen products that helps us deliver great
customer experiences.”
Results
- Stephen Weinberg
Director of Site Reliability Engineering,
Morningstar

94. Thank you
Lee Atchison ∙ Senior Director Strategic Architecture
New Relic
leeatchison@leeatchison

95. Safe Harbor
This document and the information herein (including any information that may be incorporated by reference) is provided for
informational purposes only and should not be construed as an offer, commitment, promise or obligation on behalf of New Relic, Inc.
(“New Relic”) to sell securities or deliver any product, material, code, functionality, or other feature. Any information provided hereby is
proprietary to New Relic and may not be replicated or disclosed without New Relic’s express written permission.
Such information may contain forward-looking statements within the meaning of federal securities laws. Any statement that is not a
historical fact or refers to expectations, projections, future plans, objectives, estimates, goals, or other characterizations of future
events is a forward-looking statement. These forward-looking statements can often be identified as such because the context of the
statement will include words such as “believes,” “anticipates,”, “expects” or words of similar import.
Actual results may differ materially from those expressed in these forward-looking statements, which speak only as of the date hereof,
and are subject to change at any time without notice. Existing and prospective investors, customers and other third parties transacting
business with New Relic are cautioned not to place undue reliance on this forward-looking information. The achievement or success of
the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and
are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause the actual results,
performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further
information on factors that could affect such forward-looking statements is included in the filings we make with the SEC from time to
time. Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at http://ir.newrelic.com or the
SEC’s website at www.sec.gov.
New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law. New
Relic makes no warranties, expressed or implied, in this document or otherwise, with respect to the information provided.