webinar - life's too short for cloud without analytics

Life’s Too Short…... for Cloud without Analytics Monitoring the Dynamic Nature of Cloud ComputingLee Atchison, Principal Cloud Architect and Advocate at New Relic, Inc.

Confidential ©2008-16 New Relic, Inc. All rights reserved.

@leeatchison leeatchison

▪Today’s webinar is being recorded. A link to the recording will be emailed to all registrants shortly after.

▪Please be sure to ask any questions via the “questions panel”

▪There is a brief survey after the webinar for any additional questions or feedback.

2

Housekeeping

Confidential ©2008-15 New Relic, Inc. All rights reserved.

3Confidential ©2008-16 New Relic, Inc. All rights reserved.

Who am I?

Lee AtchisonPrincipal Cloud Architectand Advocate

Specialize in:Cloud computingServices & Microservices

Scalability, Availability

28 years in industry7 in Amazon Retail & AWS(Built SW/VG AppStore, AWS Elastic Beanstalk)

4 in New Relic(Architecture Lead, Cloud, Service Migration)



We want better apps faster

DynamicEnvironment

BetterData Center

How do we use the cloud to accomplish this?


Cloud as a Better Data Center


Cloud as a “Better Data Center”

Resources are allocated to uses, just like in

a data center




a data center

Provisioning process is faster




a data center

Lifetime of components is relatively long





a data center

Lifetime of components is relatively long


Capacity planning is still important and

still applies


Why use a “Better Data Center”?



Add new Capacity(faster)



Improve ApplicationAvailability

(redundancy)




ComplianceImprove ApplicationAvailability

(redundancy)



Who is impacted?

Better DataCenter

Operations Development


Who is impacted?

Better DataCenter

Can I scale my server fleet?Can apps run anywhere?How do they perform in the cloud?

Operations Development


Who is impacted?

Better DataCenter


Operations

Data center is a data center…

Development


Who is impacted?

Better Data Center

Faster Application Launch / Deploy

=

Better DataCenter


Operations


Development


How do I monitor it?Similar to monitoring any other data center…


Monitoring an applicationTypical Server / EC2 Instance• Application &

Application Microservices• Server OS• Hardware (virtual)

EC2 Instance

Application &

Application Microservice

s

Server OS

Server (Virtual)Hardware


AWS MonitoringCloudWatch• Monitors:

– EC2 instance– Virtualization– Hardware– [CPU / Disk / Networking]

• Doesn’t know about:– Server OS– Memory / Filesystem– Processes– Application

• Latency• Error rates• Internal insights

EC2 Instance

Application &


s

Server OS

Server (Virtual)HardwareCloudWatch

AWS CONSOLE


New Relic MonitoringNew Relic• Monitors (Server):

– How O.S. is performing– Processes– Hardware

• Monitors (Application):– App health– App performance– Microservices

• Doesn’t know– Virtualization

EC2 Instance

Application &


s

New RelicApplicationMonitoring

Server OS


New RelicServer

Monitoring

CloudWatch

DASHBOARDS

AWS CONSOLE


AWS New Relic work togetherAWS / CloudWatch• Visibility into virtualization• CPU / Disk / Networking

New Relic• CPU / Disk / Networking• Memory / Filesystem• Processes• Infrastructure components• Application / Microservices:

– Latency– Error rates– App insights

EC2 Instance

Application &


s

New RelicApplicationMonitoring

Server OS


New RelicServer

Monitoring

CloudWatch

DASHBOARDS

CloudWatch

monitors

New Relic monitors

AWS CONSOLE


Cloud as a Dynamic Tool


Cloud as a “Dynamic Tool for Dynamic Apps”

Use only the

resources you need



Use only the

resources you need

Allocate / de-allocate

resources on the fly



Use only the

resources you need

Resource allocation is an integral part of

your application architecture

Allocate / de-allocate

resources on the fly


Dynamic Cloud

Resources are:

Application is aware of and is controlling traditional OPs

resourcesDe-

allocatedConsume

dAllocated

Auto Scale


Dynamic Cloud

Docker containers:• Quicker / cheaper startup /

shutdown than EC2 instances• Easy to consume Docker

containers much like you do “processes”

• Perform jobs:– In a script– Off of some queue of job

requests


Dynamic Cloud

100

10K

1M

3.7 M

83 days 333 days

Docker Container Age(Count vs. Hours)


Dynamic Cloud

950,00011% under one minute

Docker Container Age(by Minute Under and Hour)


EC2 Auto Scaling

Dynamic Cloud Technologies

Mobile / IoT

Dynamic routing

Load balancing

Data transport

Queues and notifications

Docker

Dynamic Cloud is about scaling


How do I monitor the Dynamic Cloud?Dynamic Cloud has unique monitoring requirements…


Responsibility (Dynamic Cloud)

Server OS


Application &

Application Microservic

es

Application &


es

Application &


es

Provisioning

Responsible for the parts you care about• Application &

Application Microservices

Let cloud manage rest• Infrastructure• Allocation/Provisioning• Scaling


AWS Infrastructure New Relic work together

Server OS


DASHBOARDS

Application &


es

Application &


es

Application &


es

ProvisioningAWS CONSOLE



Server OS


DASHBOARDS

Application &


es

Application &


es

Application &


es

ProvisioningAWS CONSOLE



Server OS


DASHBOARDS

Application &


es

Application &


es

Application &


es

ProvisioningCloudWatch

& AWS monitoring

New Relic monitors

AWS CONSOLE


How do you monitor this?

Server OS


Application &


es

Application &


es

Application &


es

Provisioning

?How do you monitor this?


Where did it go? It was just here!!!

? The thing you monitored 10 minutes ago…...doesn’t exist

anymore!


Dynamic Cloud

950,00011% under one minute

Docker Container Age(by Minute Under and Hour)


Monitoring the Dynamic CloudVery different than monitoring traditional Data Center components

Monitor theCloud Components

themselves

Monitor the lifecycle of the

Cloud Components


Who is impacted by Dynamic Cloud?

Better DataCenter


Operations


Development

DynamicCloud



Better DataCenter


Operations


Development

DynamicCloud

What is a container?Why do I care??It was just here, where did it go???



Better DataCenter


Operations


Development

DynamicCloud

What is a container?Why do I care??It was just here, where did it go???

Cloud architecture is integral to the application architectureDevelopers deeply involved in cloud activities


Change is speeding up

TraditionalData Center

CloudData Center

DynamicCloud

Dynamic Cloud enables better applications faster.

Good Better Best

The way you’ve done things in the past won’t work in the future.


Dynamic Cloud

EC2Server running

application / processes

Docker container

Process running a command

This ishard

Things happen faster because of…


Dynamic Cloud

EC2Server running

application / processes

Docker container

Process running a command

LambdaFunction performing a task or operation


The Future with Lambda


Microcomputing & AWS Lambda

• Newest entrance to the “dynamic cloud”

• Provides event driven compute capabilities


Microcomputing & AWS Lambda

• No infrastructure to provision• Massively shared infrastructure


Why use Lambda?Lambda scripts

Run in response to a state change or action in the cloud

Stateless, “filters”Perform quick actions

Virtually no startup/shutdown

cost


AWS Lambda

S3Bucket

DynamoDB

APIGateway

SQS

RESOURCESSOME

• Takes an event from an AWS resource (A Trigger)


AWS Lambda

S3Bucket

DynamoDB

APIGateway

SQS

RESOURCESSOME

LambdaScript


• Creates an instance to execute

LambdaInstance


AWS Lambda

S3Bucket

DynamoDB

APIGateway

SQS

RESOURCESSOME

S3Bucket

APIGateway SQS

RESOURCESSOMELambdaScript



• Can impact original or different AWS Resource Lambda

Instance


AWS Lambda

S3Bucket

DynamoDB

APIGateway

SQS

RESOURCESSOME

S3Bucket

APIGateway SQS

RESOURCESSOMELambdaScript

Lambda

Instance

Lambda

Instance Lambd

aInstanc

eLambd

aInstanc

eLambd

aInstanc

e Lambda

Instance

Lambda

Instance

Lambda

Instance Lambd

aInstanc

e



• Can impact original or different AWS Resource

• Any number of instances can run at a time


Lambda example #1:

Photo Management App


Photo management application

User

UploadFile

S3 BucketImageImport

• Photos uploaded to S3



User

UploadFile


S3 BucketImage

Thumbnails

View Thumbnai

l

LambdaScript

• Photos uploaded to S3• Lambda script creates

thumbnails



User

ImageDatabase

UploadFile


S3 BucketImage

Thumbnails

LambdaScript

View Thumbnai

l

LambdaScript


thumbnails• Lambda script updates

metadata in database



User

ImageDatabaseApplication

UploadFile


S3 BucketImage

Thumbnails

LambdaScript

AppInteraction

s

View Thumbnai

l

LambdaScript


thumbnails• Lambda script updates

metadata in database• Application only has

to deal with metadata editing, not photo / file management


Lambda example #2:

Mobile Game App


Mobile game platform

APIGateway

LambdaScript

LambdaScript

LambdaScript

Mobile PhoneApplication Users

Database

• Cloud platform hosts an API for mobile app

– API Gateway• Lambda scripts

implement the API• Lambda scripts

manipulate database• Extremely high

scale possible– No infrastructure


Monitoring Lambda Scripts

Less like server monitoring / More like web application

monitoring

We Care About

We Don’t Care About

• Run time (average, extremes – TP90/TP99)

• Statistical metrics• Error rates and

other deviations from norm

• “Drill down” into individual “runs”

• Details about all ”runs”

• Server / infrastructure metrics


Monitoring LambdaMore like application performance monitoring than infrastructure monitoring


Change is speeding up

TraditionalData Center

CloudData Center

DynamicCloud

Dynamic Cloud enables better applications faster.The rate of change is increasing…

Good Better Best

The way you’ve done things in the past won’t work in the future.


Monitoring just the server

EC2 Instance

Application &


s

Server OS


Worked when rate of change was low…

AWS CONSOLE

Monitoring just the server

Server OS


Application &


es

Application &


es

Application &


es

Provisioning

Insufficient in the cloud:

• Rate of change is faster• Problems come up quicker• “Server” isn’t a server anymore• “Provisioning” isn’t provisioning anymore

You need top to bottom monitoring…

You need full stack accountability...


New Relic enables accountability betweenyour code & AWS

Customers

Mobile / Apps / Browser

On-Premises

On Premises Relational

Data

EC2

AWSContainer Service

AWS RDSSynthetic Customers

S3

NoSQL

AWS Storage Services

Your Responsibilities Application code & 3rd party

services App architecture Customer experience On-Premises components

NoSQLAWS Responsibility: Service Availability & Performance Provisioning & operation of DC Isolation & security of resources Service maintenance & innovation

Architecting for ScaleBy: Lee AtchisonPublished by: O’Reilly Media, Available: June 2016www.architectingforscale.com

Want to Learn More?

©2008-15 New Relic, Inc. All rights reserved.

Thank you.

Lee AtchisonPrincipal Cloud Architect and Advocate at New Relic, Inc.

Architecting for ScalePublished by: O’Reilly Media, Available: June 2016www.architectingforscale.com



Safe HarborThis 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.

webinar - life's too short for cloud without analytics

Technology