identifying workloads to move to the cloud

34
Identifying Workloads to Move to the Cloud October 4, 2011 Watch the video of this webinar

Upload: rightscale

Post on 20-Aug-2015

1.131 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Identifying Workloads to Move to the Cloud

Identifying Workloads toMove to the Cloud

October 4, 2011

Watch the video of this webinar

Page 2: Identifying Workloads to Move to the Cloud

# 2

Your Panel TodayPresenting• Ryan Geyer, Sales Engineer, RightScale • Pavel Pragin, PS Architect, RightScale

Q&A • Jason Dorfman, Account Manager, RightScale

Please use the “Questions” window to ask questions any time!

Page 3: Identifying Workloads to Move to the Cloud

# 3

Agenda• Characteristics of Ideal Workloads

• Scalable Web Apps – Social Media/Gaming• Batch Processing – Encoding• Disaster Recovery (DR)• Multi-Region/Cloud

• Characteristics of Bad Workloads• Live Q&A

Please use the “Questions” window to ask questions any time!

Page 4: Identifying Workloads to Move to the Cloud

# 4

CLOUD IS FOR EVERYONE, NOT EVERYTHING

EveryFirm

NotEveryApp

Page 5: Identifying Workloads to Move to the Cloud

# 5

Application Portfolio

Requirements Filter

Resource Pools

App 1

App 2

App 3

Performance

Cost

Compliance

Reliability

Security

RightScale Delivers Workload Deployment Freedom

It’s about using multiple resource pools, not choosing one.

App N

App 1

App 2

App 3

App N

Internal DC

Private Cloud 1

Public Cloud

Page 6: Identifying Workloads to Move to the Cloud

# 6

Characteristics of Great Workloads • Unpredictable load or explosive growth potential

• Social gaming• Software as a service product launch• eCommerce• Blogs

• Partial utilization• Seasonal eCommerce load• Month/Quarter/Year end data consolidation (batch processing)

• Applications that are easily parallelized (scale out, not up)• Media streaming• Websites/applications

Page 7: Identifying Workloads to Move to the Cloud

Identifying Workloads to Move to the Cloud

Scalable Web Apps

Page 8: Identifying Workloads to Move to the Cloud

# 8

Scalable Web AppsChallenges

• Unpredictable traffic spikes• Need to scale exponentially• Need high level of automation

Page 9: Identifying Workloads to Move to the Cloud

# 9

Scalable Web AppsCloud Strengths

• Autoscaling capability• Unlimited resources on demand• Pay for what you use• RightScale enables automation and eases operations

Page 10: Identifying Workloads to Move to the Cloud

# 10

Example Scalable Web App Architecture

Page 11: Identifying Workloads to Move to the Cloud

# 11

Example Scalable Web App Architecture

AMQP

Page 12: Identifying Workloads to Move to the Cloud

# 12

Example Scalable Web App Architecture

Load Balanced Riak

AMQP

Page 13: Identifying Workloads to Move to the Cloud

# 13

Example Scalable Web App Architecture

MySQL DB Tier

Page 14: Identifying Workloads to Move to the Cloud

# 14

Example Scalable Web App Architecture

MySQL DB Tier

Memcached

Page 15: Identifying Workloads to Move to the Cloud

# 15

Example Scalable Web App Architecture

Auto Scaling Python App Tier

Page 16: Identifying Workloads to Move to the Cloud

Identifying Workloads to Move to the Cloud

Batch Processing

Page 17: Identifying Workloads to Move to the Cloud

# 17

Batch ProcessingChallenges

• Need extremely high processing power• Need to process huge workloads• Need to process workloads fast• Fluctuating utilization cycle

Page 18: Identifying Workloads to Move to the Cloud

# 18

Batch ProcessingCloud Strengths

• Autoscaling on demand using metrics• Bring up large numbers of servers fast• Throw huge numbers of servers at the problem• Pay for what you use and when you need it

Page 19: Identifying Workloads to Move to the Cloud

# 19

Example Batch Processing Architecture

Page 20: Identifying Workloads to Move to the Cloud

# 20

Example Batch Processing Architecture

Auto Scaling Application Tier (Squeeze)

Page 21: Identifying Workloads to Move to the Cloud

# 21

Example Batch Processing Architecture

MySQL DB Tier

Page 22: Identifying Workloads to Move to the Cloud

Identifying Workloads to Move to the Cloud

Disaster Recovery

Page 23: Identifying Workloads to Move to the Cloud

# 23

Disaster RecoveryChallenges

• Need infrastructure in a different location• Don’t want to pay for hardware and not use it• Need to be able to launch a new deployment anywhere fast• Affordable disaster recovery

Page 24: Identifying Workloads to Move to the Cloud

# 24

Disaster RecoveryCloud Strengths

• Use any public and/or private cloud• Run a scaled down deployment replica

• Replicating slave DB is the only “always on” server

• Use RightScripts and ServerTemplates to spin up deployments fast anywhere• Launch the rest of the servers in your deployment• Promote replicating slave DB to master

• High level of automation for smoother failover

Page 25: Identifying Workloads to Move to the Cloud

# 25

Example Disaster Recovery Architecture

Page 26: Identifying Workloads to Move to the Cloud

# 26

Example Disaster Recovery Architecture

Slave DB’s (Always On)

Page 27: Identifying Workloads to Move to the Cloud

Identifying Workloads to Move to the Cloud

Multi-Region / Multi-Cloud

Page 28: Identifying Workloads to Move to the Cloud

# 28

Multi-Region / Multi-CloudChallenges

• No public cloud in needed location• Need to burst to public cloud• Need better performance• High cost of public cloud at huge scale• Challenges and costs of DR

Page 29: Identifying Workloads to Move to the Cloud

# 29

Multi-Region / Multi-CloudCloud Strengths

• RightScale enables you to deploy in multiple clouds and regions seamlessly

• Private cloud can be set up in any datacenter anywhere• Burst to public cloud for more resources• Achieve better performance with private cloud• Save money by using your own hardware with private cloud at

large scale

Page 30: Identifying Workloads to Move to the Cloud

# 30

Example Multi-Region/Multi-Cloud Workload Architecture

Page 31: Identifying Workloads to Move to the Cloud

# 31

Example Multi-Region/Multi-Cloud Workload Architecture

Global Traffic Management via DNS

Page 32: Identifying Workloads to Move to the Cloud

# 32

Example Multi-Region/Multi-Cloud Workload Architecture

Database Tier Replicated over SSL

Page 33: Identifying Workloads to Move to the Cloud

# 33

Characteristics of Bad Workloads• Very high performance applications (Disk I/O and Network)

• Databases with very high I/O requirements• Application with very high I/O requirements• No tolerance for I/O performance fluctuations• High performance storage• Poor application design• Legacy and Enterprise Apps

• Low Latency• Database Replication and Clustering that requires very high network

throughput• Legacy and Enterprise Apps• Need for high performance network storage

• Hardware dependency

Page 34: Identifying Workloads to Move to the Cloud

# 34

Getting Started and Q&A

Contact RightScale:(866) [email protected] www.rightscale.com

More InfoWebinar archive: RightScale.com/webinars

Whitepapers: RightScale.com/whitepapers

Free Edition: RightScale.com/free

Next up in the “I’m in the Cloud – Now What?” series:

October 13Optimizing Your Cloud Applications in RightScale

- Rafael Saavedra, VP Engineering, RightScale

www.RightScale.com/now-what

RightScale ConferenceNov 8-9 in Santa Clara, CAwww.RightScale.com/Conference•Attend technical breakout sessions•Talk with RightScale customers•Ask questions at the Genius Bar