The media is highlighting scores of stories about companies that have moved from one public cloud to another for business or technical reasons. Regardless of whether you are running on AWS, Azure, or Google, there will likely come a time that you’ll want to consider switching cloud providers. Whether you are contemplating a move now or just want to keep your options open in the future, you will need to consider a variety of cost, service, and technical factors. In this webinar, we’ll walk you through the evaluation process of migrating to another cloud provider and highlight the pros and cons.
Boost Fertility New Invention Ups Success Rates.pdf
Should You Move Between AWS, Azure, or Google Clouds? Considerations, Pros and Cons
1. SHOULD YOU MOVE BETWEEN
AWS, AZURE, AND GOOGLE CLOUDS?
CONSIDERATIONS AND PROS & CONS
2. • Kim Weins
• VP Marketing & Cloud Cost Strategy, RightScale
• Raphael Simon
• CTO, RightScale
Presenters
3. • Top reasons to consider other clouds
• Migration vs portability
• Comparing cloud services
• Comparing features
• Comparing costs
• Technical considerations
Agenda
2
4. Two Solutions from RightScale
RightScale
Cloud Management Platform
Orchestrate, automate and govern workloads
across all your environments.
VIRTUAL
SERVERS
PUBLIC
CLOUDS
ANY CLOUD
SERVICE
PRIVATE
CLOUDS
BARE METAL
SERVERS
CONTAINER
CLUSTERS
RightScale
Optima
Work collaboratively across the organization
to manage and optimize clouds costs.
Orchestration
Cloud Workflow
Plugins
Monitoring
Access Control
Accounts/Groups
Access/Permissions
Tags
Policies
Cost
Security/Compliance
Operational
RIGHTSCALE
CMP ENGINE
EXTENSIBLE ORCHESTRATION API
5. RightScale is a Leader in Both 2018 Forrester Waves:
Cloud Cost Optimization and Hybrid Cloud Management
The Forrester Wave™ is copyrighted by Forrester Research, Inc. Forrester and Forrester Wave™ are trademarks of Forrester Research, Inc. The Forrester Wave™ is a graphical
representation of Forrester's call on a market and is plotted using a detailed spreadsheet with exposed scores, weightings, and comments. Forrester does not endorse any vendor,
product, or service depicted in the Forrester Wave™. Information is based on best available resources. Opinions reflect judgment at the time and are subject to change
9. ● Cost considerations
● Vendor leverage
● Vendor diversity
● Desire to use unique services
● Need for particular regions
● Strategic reasons
6 Reasons Companies Move Public Clouds
8
10. • Migration (one-time)
• Onboard – migrate to cloud for first time
• Cloud to Cloud – move from cloud A to cloud B
• Portability (ongoing)
• Semi-portable – architected to move later with some effort
• Fully-portable – can deploy seamlessly on multiple supported clouds
Migration vs Portability
9
11. Use Cases for Portability
• Most Common
• Avoid lock-in
• Ability to move at some point
• Best venue approach (typically for batch/dev/qa)
• Geography, Cost, Features
• Lifecycle approach
• Dev/Test vs. Staging/Production on different resource pools
• Disaster Recovery
• Less Common
• Split-tier architectures
• Cloud-bursting
12. 1. What are your motivations/goals?
2. Map services you use across clouds
• Plan for how to deal with services that are missing or significantly
different
3. Map regions you use across clouds
4. Map detailed billing items
• Instances, Storage, Network, Other Services
5. Model discounts for each cloud
6. Review technical considerations
7. Make a decision based on services, regions, costs and your
goals
Steps to Take Before You Make the Move
11
17. • Same country, closest region
• Same country, lowest price nearby region
• Example: Currently in AWS US-East (N. Virginia)
• Consider Google South Carolina instead of Northern Virginia
• Consider nearby countries in some cases
• Example: Currently in Google London
• Consider Azure North Europe (Ireland) or West Europe (Netherlands)
Region Approaches When Moving
16
20. • Example one: On AWS, considering move to Google
• Using NFS from AWS Marketplace
• No equivalent on Google at the time (now Google Cloud Filestore is in
Beta)
• Decision to stay on AWS and switch to AWS EFS
• Example 2: On AWS, considering move to Google
• Google ILB (Internal Load Balancer) was missing a feature the customer
needed
• Decision to move anyways
• Customer “rolled their own” with Nginx
What If It’s a Mismatch?
19
22. VM Type AWS AWS Mem
AWS
Disk
Google
Google
Mem
Google
Disk
Azure
Azure
Mem
Azure
Disk
Standard
2 vCPU
w SSD
m5d.large 8 75 n1-standard-2 7.5 375 D2s v3 8 16
Standard
2 vCPU
no SSD
m5.large 8 0 n1-standard-2 7.5 0 D2s v3 8 16
Highmem
2 vCPU
w SSD
r3.large 15 32 n1-highmem-2 13 375 E2s v3 16 16
Highmem
2 vCPU
no SSD
r4.large 15.25 0 n1-highmem-2 13 0 E2s v3 16 16
Highcpu
2 vCPU
w SSD
c5d.large 4 50 n1-highcpu-2 1.8 375 F2 v2 4 16
Highcpu
2 vCPU
no SSD
c5.large 4 0 n1-highcpu-2 1.8 0 F2 v2 4 16
VM Comparisons
Source: RightScale
Different amounts of
memory on HighCPU
As of Jul 10, 2018
23. VM Type
US
Linux
AWS OD
Hourly
Google OD
Hourly
Azure OD
Hourly
AWS OD
/GB RAM
Google OD
/GB RAM
Azure OD
/GB RAM
Standard
2 vCPU
w Local SSD
$0.113 $0.136 $0.096 $0.014 $0.018 $0.012
Standard
2 vCPU
no Local disk
$0.096 $0.095 $0.100 $0.012 $0.013 $0.013
Highmem
2 vCPU
w Local SSD
$0.166 $0.159 $0.133 $0.011 $0.012 $0.008
Highmem
2 vCPU
no Local disk
$0.133 $0.118 $0.133 $0.009 $0.009 $0.008
Highcpu
2 vCPU
w Local SSD
$0.096 $0.112 $0.085 $0.024 $0.062 $0.021
Highcpu
2 vCPU
no Local disk
$0.085 $0.071 $0.085 $0.021 $0.039 $0.021
Comparing On-Demand Hourly Spend
Source: RightScaleAs of Jul 10, 2018
24. • AWS - Different instance families for with or without local disk
• m3 - includes local (ephemeral) instance storage
• m4 - doesn’t include instance storage -- EBS backed and optimized
• Newest m series (m5) doesn’t include local storage
• Azure - Includes local storage, amount is declining
• D2 v3 has 50 GB of temporary (local) storage
• D2 v2 had 100 GB of temporary (local) storage
• Use Managed Disks for persistent storage
• Google - Persistent Disk is most common
• There is a local disk option but it comes in 375 GM increments
Disk Storage Considerations: Local vs Attached
23
25. AWS Azure Google
Service Name EBS Managed Disks Persistent Disk
Availability SLA 99.99% 99.9% 99.95%
Volume Types Cold HDD
Throughput Optimized HDD
General Purpose SSD
PIOPs SSD
Magnetic (previous gen)
Standard
Premium (SSD)
Standard
SSD
IOPs/GB for SSD GP SSD = 3
PIOPS SSD up to 50/GB
1.8 to 4.9 - fixed by disk
type
30
Block/Disk Storage Overview
24
Source: RightScaleAs of Jul 10, 2018
26. AWS
monthly cost
Azure
monthly cost
Google
monthly cost
Name of Services EBS Managed Disk Persistent Disk
Magnetic
500 GB
$22.50
$16.64
E20
$20.00
SSD
500 GB, 1000 IOPs
$50.00
$66.56
P20 – 2300 IOPs
$85.00
Includes 15,000 IOPs
SSD
500 GB, 2000 IOPs
$192.50
PIOPs SSD
$66.56
P20 – 2300 IOPs
$85.00
Includes 15,000 IOPs
SSD
500 GB, 5000 IOPs
$387.50
PIOPs SSD
$122.88
P30 – 5000 IOPs
$85.00
Includes 15,000 IOPs
Snapshots
500 GB
$25.00
$25.00
$13.00
Block/Disk Storage - Scenarios
Source: RightScaleAs of Jul 10, 2018
27. AWS Azure Google
Service Name S3 Azure Storage (Blobs) Google Cloud Storage
Hot S3 Standard Hot Blob Storage GCS
Cool S3 Standard – Infrequent Access Cool Blob Storage GCS Nearline
Cold (Archival) Glacier Archive Blob Storage GCS Coldline
# Object Limits Unlimited Unlimited Unlimited
Object Size Limit 5 TB 4.75 TB (Block blobs) 5TB
Object Storage - Overview
26
Source: RightScaleAs of Jul 10, 2018
28. AWS
monthly cost
Azure
monthly cost
Google
monthly cost
Name of Services S3/Glacier Blob Storage GCS
Hot Multi-Region
1000 GB stored
1000 GB transferred
$56.00 $56.80 $26.00
Hot Single Region
1000 GB stored
$23.00 $18.40 $20.00
Cool Single Region
1000 GB stored
$12.50 $10.00 $10.00
Cold Single Region
1000 GB stored
$4.00 $2.00 $7.00
Object Storage - Scenarios
Source: RightScaleAs of Jul 10, 2018
29. AWS
Service
AWS Pricing
Metrics
Azure
Service
Azure Pricing
Metrics
Google
Service
Google Pricing
Metrics
DBaaS RDS
Instance type
DB storage,
Data transfer
SQL
Database
Compute
units,
DB storage,
Data transfer
Cloud SQL
Instance, PD,
Storage, Egress
Monitoring Cloudwatch
Detailed
monitoring,
custom metrics,
API requests
Azure
Monitor
Custom
Metrics,
metric queries
Stackdriver
Non-GCP
metrics, API
calls
Stream
processing
Kinesis
GBs ingested,
GBs converted
Event
Hubs
# ingress
events,
througput
used
Pub/Sub GBs ingested
Pricing Metrics on Other Services May Vary