identifying workloads to move to the cloud
TRANSCRIPT
Identifying Workloads toMove to the Cloud
October 4, 2011
Watch the video of this webinar
# 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!
# 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!
# 4
CLOUD IS FOR EVERYONE, NOT EVERYTHING
EveryFirm
NotEveryApp
# 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
# 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
Identifying Workloads to Move to the Cloud
Scalable Web Apps
# 8
Scalable Web AppsChallenges
• Unpredictable traffic spikes• Need to scale exponentially• Need high level of automation
# 9
Scalable Web AppsCloud Strengths
• Autoscaling capability• Unlimited resources on demand• Pay for what you use• RightScale enables automation and eases operations
# 10
Example Scalable Web App Architecture
# 11
Example Scalable Web App Architecture
AMQP
# 12
Example Scalable Web App Architecture
Load Balanced Riak
AMQP
# 13
Example Scalable Web App Architecture
MySQL DB Tier
# 14
Example Scalable Web App Architecture
MySQL DB Tier
Memcached
# 15
Example Scalable Web App Architecture
Auto Scaling Python App Tier
Identifying Workloads to Move to the Cloud
Batch Processing
# 17
Batch ProcessingChallenges
• Need extremely high processing power• Need to process huge workloads• Need to process workloads fast• Fluctuating utilization cycle
# 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
# 19
Example Batch Processing Architecture
# 20
Example Batch Processing Architecture
Auto Scaling Application Tier (Squeeze)
# 21
Example Batch Processing Architecture
MySQL DB Tier
Identifying Workloads to Move to the Cloud
Disaster Recovery
# 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
# 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
# 25
Example Disaster Recovery Architecture
# 26
Example Disaster Recovery Architecture
Slave DB’s (Always On)
Identifying Workloads to Move to the Cloud
Multi-Region / Multi-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
# 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
# 30
Example Multi-Region/Multi-Cloud Workload Architecture
# 31
Example Multi-Region/Multi-Cloud Workload Architecture
Global Traffic Management via DNS
# 32
Example Multi-Region/Multi-Cloud Workload Architecture
Database Tier Replicated over SSL
# 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
# 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