2. Scaling on AWS for the First 10 Million Users
• ME: Chris Munns – Solutions Architect – Amazon Web
Services – munns@amazon.com
• YOU: Here to learn more about scaling infrastructure
on AWS
• TONIGHT: about best practices and things to think
about when building for large scale
11. US-WEST (Oregon)
EU-WEST (Ireland)
ASIA PAC (Tokyo)
US-WEST (N. California)
SOUTH AMERICA (Sao Paulo)
US-EAST (Virginia)
AWS GovCloud (US)
ASIA PAC
(Sydney)
Regions
ASIA PAC
(Singapore)
12. US-WEST (Oregon)
EU-WEST (Ireland)
ASIA PAC (Tokyo)
US-WEST (N. California)
SOUTH AMERICA (Sao Paulo)
US-EAST (Virginia)
AWS GovCloud (US)
ASIA PAC
(Sydney)
Availability Zones
ASIA PAC
(Singapore)
13. • $5.2B retail business
• 7,800 employees
• A whole lot of servers
Every day, AWS adds enough
server capacity to power that
whole $5B enterprise
17. Day One, User One:
• A single EC2 Instance
– With full stack on this host
• Web App
• Database
• Management
• etc
• A single Elastic IP
• Route53 for DNS
EC2
Instance
Elastic IP
Amazon
Route 53
User
18. “We’re gonna need a bigger box”
• Simplest approach
• Can now leverage PIOPs
• High I/O instances
• High Memory instances
• High CPU instances
• High storage instances
• Easy to change instance sizes
• Will hit an endpoint eventually
hi1.4xlarge
m2.4xlarge
m1.small
19. “We’re gonna need a bigger box”
• Simplest approach
• Can now leverage PIOPs
• High I/O instances
• High Memory instances
• High CPU instances
• High storage instances
• Easy to change instance sizes
• Will hit an endpoint eventually
hi1.4xlarge
m2.4xlarge
m1.small
20. Day One, User One:
• We could potentially get
to a few hundred to a few
thousand depending on
application complexity
and traffic
• No failover
• No redundancy
• Too many eggs in one
basket
EC2
Instance
Elastic IP
Amazon
Route 53
User
21. Day One, User One:
• We could potentially get
to a few hundred to a few
thousand depending on
application complexity
and traffic
• No failover
• No redundancy
• Too many eggs in one
basket
EC2
Instance
Elastic IP
Amazon
Route 53
User
22. Day Two, User >1:
First lets separate out
our single host into
more than one.
• Web
• Database
– Make use of a database
service?
Web
Instance
Database
Instance
Elastic IP
Amazon
Route 53
User
23. Self-Managed Fully-Managed
Database Server
on Amazon EC2
Your choice of
database running on
Amazon EC2
BringYour Own
License (BYOL)
Amazon
DynamoDB
Managed NoSQL
database service
using SSD storage
Seamless
scalability Zero
administration
Amazon RDS
Microsoft SQL,
Oracle or MySQL as
a managed service
Flexible licensing
BYOL or License
Included
Amazon
Redshift
Massively parallel,
petabyte-scale,
data warehouse
service
Fast, powerful and
easy to scale
Database Options
24. But how do I choose
what DB technology I
need? SQL? NoSQL?
30. Why start with SQL?
• Established and well worn technology
• Lots of existing code, communities, books,
background, tools, etc
• You aren’t going to break SQL DBs in your first 10
million users. No really, you won’t*
• Clear patterns to scalability
*Unless you are doing something SUPER weird with the data or
MASSIVE amounts of it, even then SQL will have a place in your stack
31. AH HA! You said “massive
amounts”, I will have
massive amounts!
32. If your usage is such that you
will be generating several TB(
>5 ) of data in the first year OR
have an incredibly data
intensive work load you might
need NoSQL
35. User >100:
First lets separate out
our single host into
more than one.
• Web
• Database
– Use RDS to make your life
easier
Web
Instance
Elastic IP
RDS DB
Instance
Amazon
Route 53
User
36. User > 1000:
Next let’s address our
lack of failover and
redundancy issues:
• Elastic Load Balancer
• Another Web instance
– In another Availability Zone
• Enable RDS Multi-AZ
Web
Instance
RDS DB Instance
Active (Multi-AZ)
Availability Zone Availability Zone
Web
Instance
RDS DB Instance
Standby (Multi-AZ)
Elastic Load
Balancer
Amazon
Route 53
User
37. • Create highly scalable applications
• Distribute load across EC2 instances
in multiple availability zones
Feature Details
Available Load balance across instances in multiple
Availability Zones
Health checks Automatically checks health of instances and
takes them in or out of service
Session stickiness Route requests to the same instance
Secure sockets layer Supports SSL offload from web and application
servers with flexible cipher support
Monitoring Publishes metrics to CloudWatch
Elastic Load
Balancer
Elastic Load Balancing
39. User >10ks-100ks:
RDS DB Instance
Active (Multi-AZ)
Availability Zone Availability Zone
RDS DB Instance
Standby (Multi-AZ)
Elastic Load
Balancer
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Amazon
Route 53
User
40. This will take us pretty far
honestly, but we care about
performance and efficiency,
so lets clean this up a bit
41. Shift some load around:
Let’s lighten the load on
our web and database
instances a bit:
• Move static content from
webs to S3 and CloudFront
• Move session/state and DB
caching to ElastiCache or
DynamoDB
Web
Instance
RDS DB Instance
Active (Multi-AZ)
Availability Zone
Elastic Load
Balancer
Amazon S3
Amazon
Cloudfront
Amazon
Route 53
User
ElastiCache
DynamoDB
42. Working with S3 - Amazon Simple Storage Service
• Object based storage for the web
• 11 9s of durability
• Good for things like:
– Static assets ( css, js, images,
videos )
– Backups
– Logs
– Ingest of files for processing
• “Infinitely scalable”
• Supports fine grained permission
control
• Ties in well with CloudFront
• Ties in with EMR
• Acts as a logging endpoint for
S3/CloudFront/Billing
• Supports Encryption at transit and at
rest
• Reduced Redundancy 1/3 cheaper
• Glacier for super long term storage
43. DynamoDB
• Provisioned throughput NoSQL
database
• Fast, predictable performance
• Fully distributed, fault tolerant
architecture
• Considerations for non-uniform
data
Feature Details
Provisioned
throughput
Dial up or down provisioned
read/write capacity.
Predictable
performance
Average single digit millisecond
latencies from SSD-backed
infrastructure.
Strong
consistency
Be sure you are reading the
most up to date values.
Fault tolerant Data replicated across
Availability Zones.
Monitoring Integrated to CloudWatch.
Secure Integrates with AWS Identity
and Access Management (IAM).
Elastic
MapReduce
Integrates with Elastic
MapReduce for complex
analytics on large datasets.
44. ElastiCache
• Hosted Memcached
– Speaks same API as traditional open source
memcached
• Scale from one to many nodes
• Self healing ( replaces dead instance )
• Very fast ( single digit ms speeds usually (or less) )
• Local to a single AZ
– So need to run different clusters across different Azs
• Data is only in memory, so not persistent
• Use AWS’s Auto Discovery client to simplify clusters
growing and shrinking without affecting your application
45. Now that our Web tier is
much more light weight, we
can revisit the beginning of
our talk..
47. Automatic resizing of compute
clusters based on demand
Trigger auto-scaling
policy
Feature Details
Control Define minimum and maximum instance pool
sizes and when scaling and cool down occurs.
Integrated to Amazon
CloudWatch
Use metrics gathered by CloudWatch to drive
scaling.
Instance types Run Auto Scaling for On-Demand and Spot
Instances. Compatible with VPC.
as-create-auto-scaling-group MyGroup
--launch-configuration MyConfig
--availability-zones us-east-1a
--min-size 4
--max-size 200
Auto-Scaling
Amazon
CloudWatch
58. SOA’ing
Move services into their own
tiers/modules.Treat each of
these as 100% whole-y separate
pieces of your infrastructure and
scale them independently.
Amazon.com and AWS do this
extensively! It offers flexibility
and greater understanding of
each component
59. Loose coupling sets you free!
• The looser they're coupled, the bigger
they scale
– Independent components
– Design everything as a black box
– Decouple interactions
– Favor services with built in redundancy and
scalability than building your own
Controller A Controller B
Controller A Controller B
Q Q
Tight Coupling
Use Amazon SQS as Buffers
Loose Coupling
60. Loose coupling + SOA = winning
In the early days, if someone has a service for
it already, opt to use that instead of building it
yourself. DON’T REINVENT THE WHEEL
Examples:
• Email
• Queuing
• Transcoding
• Search
• Databases
• Monitoring
• Metrics
• Logging
Amazon
CloudSearch
Amazon SQSAmazon SNS
Amazon Elastic
Transcoder
Amazon SWF
Amazon SES
61. On re-inventing the wheel: if
you find yourself writing
your own: queue, DNS
server, database, storage
system, monitoring tool
65. S3 Bucket
For Ingest
User
SNS Topic
RRS S3
Bucket to
Serve
content to
CloudFront
S3 Bucket
For
originals
CloudFront
Download
Distribution
SQS Queue
Size for Thumbnail
SQS Queue
Size Image for
Mobile
SQS Queue
Size Image for Web
Auto scaling
Group
Instances
Auto scaling
Group
Instances
Auto scaling
Group
Instances
66. Amazon Simple Workflow (SWF)
• Orchestration tool across your infrastructure
• Use it as a middle layer to pass messages and setup tasks to be completed
• Break down individual tasks into different workers
• You define logic between workers
• Anything that can be scripted, can be made into a worker task
• Built in retries, timeouts, logging
• Low cost, reliability, and scalability built in
Deciders Workers
YOUR CODE = &
67. S3 Bucket
For Ingest
User
SNS Topic
RRS S3
Bucket to
Serve
content to
CloudFront
S3 Bucket
For
originals
CloudFront
Download
Distribution
SQS Queue
Size for Thumbnail
SQS Queue
Size Image for
Mobile
SQS Queue
Size Image for Web
Auto scaling
Group
Instances
Auto scaling
Group
Instances
Auto scaling
Group
Instances
68. S3 Bucket
For Ingest
User
RRS S3
Bucket to
Serve
content to
CloudFront
S3 Bucket
For
originals
CloudFront
Download
Distribution
Auto scaling
Group
Instances
Auto scaling
Group
Instances
Auto scaling
Group
Instances
SWF
Instance running
decider
69. User >1mil+:
Reaching a million and above is going to require some bit
of all the previous things:
• Multi-AZ
• Elastic Load Balancer between tiers
• Auto-Scaling
• Service oriented architecture
• Serving content smartly ( S3/CloudFront )
• Caching off DB
• Moving state off tiers that auto-scale
70. User >1mil+:
RDS DB Instance
Active (Multi-AZ)
Availability Zone
Elastic Load
Balancer
RDS DB Instance
Read Replica
RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
Web
Instance
Amazon
Route 53
User
Amazon S3
Amazon
Cloudfront
DynamoDB
Amazon SQS
ElastiCache
Worker
Instance
Worker
Instance
Amazon
CloudWatch
Internal App
Instance
Internal App
Instance
Amazon SES
72. User >5mil – 10mil:
You’ll potentially start to run into issues with your
database around contention on the write master.
How can you solve it?
• Federation ( splitting into multiple DBs based on
function)
• Sharding ( splitting one data set up across multiple
hosts)
• Moving some functionality to other types of DBs (
NoSQL )
73. Database Federation
• Split up Databases by
function/purpose
• Harder to do cross function
queries
• Essentially delaying the need
for something like
sharding/NoSQL until much
further down the line
• Won’t help with single huge
functions/tables
ForumsDB
UsersDB
ProductsDB
74. Sharded Horizontal Scaling
• More complex at the
application layer
• ORM support can help
• No practical limit on scalability
• Operation
complexity/sophistication
• Shard by function or key space
• RDBMS or NoSQL
User ShardID
002345 A
002346 B
002346 C
002347 B
002349 A
A
B
C
75. User >5mil – 10mil:
You’ll potentially start to run into issues with speed and
performance of your applications.
• Need to make sure you have
monitoring/metrics/logging in place
– If you can’t build it internally, out source it! ( 3rd party SaaS )
• Pay attention to what customers are saying works well
vs what doesn’t
• Really try to work on squeezing as much performance
out of each service/component
78. AWS Marketplace & Partners can help
• Customer can find, research, buy
software
• Simple pricing, aligns with EC2 usage
model
• Launch in minutes
• Marketplace billing integrated into your
AWS account
• 700+ products across 20+ categories
Learn more at: aws.amazon.com/marketplace
79. User >5mil – 10mil:
Managing your infrastructure will become an ever
increasing important part of your time. Use tools to
automate repetitive tasks.
• Tools to manage AWS resources
• Tools to manage software and configuration on your
instances
• Automated data analysis of logs and user actions
80. AWS Application Management Solutions
Elastic Beanstalk OpsWorks CloudFormation EC2
Convenience Control
Higher-level Services Do it yourself
81. Host based Configuration Management
Two big players:
– Opscode Chef
– PuppetLabs Puppet
• Both do more or less the same thing
• Both have syntax that isn’t too dissimilar
• Use these one of these along side one of the tools
from the previous slide
• Spend the time required to learn them
• Can’t scale easily with out something like this
83. • Multi-AZ your infrastructure
• Make use of self scaling services ( ELB, S3, DynamoDB, SQS,
SWF, SES, etc )
• Build in redundancy at every level.
• Start SQL. Seriously.
• Move to NoSQL if it really makes sense
• Leverage managed/low touch services
• Split tiers into individual services ( SOA )
• Use Auto-scaling once you’re ready to
• Use automation tools in your infrastructure
• Make sure you have good metrics/monitoring/logging tools
in place
• Don’t reinvent the wheel
84. Putting all this together
means we should now easily
be able to handle 10+
million users!
85. a few words of caution on
what not to waste time on…
91. User >10mil:
A lot of what we covered today will
get you potentially into the high 10s of
millions. Iterating on top of the
patterns seen here will get you up and
over 100 million users.
92. User >10mil:
• More fine tuning of your application
• More SOA of features/functionality
• Going from Multi-AZ to Multi-Region
• Needing to start potentially building
custom solutions
• Deep analysis of your whole stack
This is a point of reference about our scale- in 2003, Amazon.com was a $5+ Billion technology powered retail business. When we measured the capacity growth rate of our current AWS environments, we found that we add enough server capacity to power all of the 2003 era Amazon business, EVERY DAY.As an additional point of comparison, $5Billion revenue puts you right around 400 in the Fortune 500- that means that we’re adding enough capacity to power a pretty big stand alone company- For some perspective on this, some examples of companies with revenues right around $5 Billion include Charles Schwab, Clorox, Harley Davidson and VMWare.
Over 30 services
Over 30 services, the 25 major services as seen in the console
18 instance types
18 instance types
18 instance types
Amazon EC2 enables our partners and customers to build and customize Amazon Machine Images (AMIs) with software based on your needs. These are the database servers available for use today within Amazon EC2: Oracle Database 11g,Microsoft SQL Server Standard,MySQL Enterprise,IBM DB2,IBM Informix Dynamic Server. http://aws.amazon.com/ec2/Amazon Relational Database Service (Amazon RDS) is a web service that makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing you up to focus on your applications and business. Amazon RDS gives you access to the capabilities of a familiar MySQL or Oracle database. This means that the code, applications, and tools you already use today with your existing databases can be used with Amazon RDS. Amazon RDS automatically patches the database software and backs up your database, storing the backups for a user-defined retention period and enabling point-in-time recovery. You benefit from the flexibility of being able to scale the compute resources or storage capacity associated with your relational database instance via a single API call. In addition, Amazon RDS for MySQL makes it easy to use replication to enhance availability and reliability for production databases and to scale out beyond the capacity of a single database deployment for read-heavy database workloads. As with all Amazon Web Services, there are no up-front investments required, and you pay only for the resources you use. http://aws.amazon.com/rds/Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. With a few clicks in the AWS Management Console, customers can launch a new Amazon DynamoDB database table, scale up or down their request capacity for the table without downtime or performance degradation, and gain visibility into resource utilization and performance metrics. Amazon DynamoDB enables customers to offload the administrative burdens of operating and scaling distributed databases to AWS, so they don’t have to worry about hardware provisioning, setup and configuration, replication, software patching, or cluster scaling. http://aws.amazon.com/dynamodb/Amazon Redshift is a managed data warehouse service in the Amazon cloud. Redshift is optimized for data sets ranging from 100’s of GB to peta-byte scale. It uses columnar storage to compress and accelerate scan operations against large data sets, while providing a SQL interface for easy integration with reporting and query tools. All Redshift operations occur as massively parallel processes, including data loading, query, resizing, backup and restore. Redshift users can provision a cluster and load data directly from S3 in a few minutes, and be assured that their data is protected by VPC and encryption, both at rest and in-flight (via SSL).
Most of you will get to this point and pretty well off honestly. You can take this really pretty far for most web applications. But we want to be smarter and more efficient than this, and also what about performance?
Most of you will get to this point and pretty well off honestly. You can take this really pretty far for most web applications. But we want to be smarter and more efficient than this, and also what about performance?
AWS Marketplace is the AWS Online Software Store Customer can find, research, buy software including developer toolsWith AWS Marketplace, the simple hourly pricing of most products aligns with EC2 usage model You can find, purchase and 1-Click launch in minutes, making deployment easyMarketplace billing integrated into your AWS account600+ products across 23 categories including bug tracking, monitoring, source control and testing
In general you can say that with Beanstalk and OpsWorks you have higher level services that abstract thingsvs the DIY world of cloudformation and EC2 and friends (cloudwatch, autoscaling, ELB)SO WHY SHOULD SOMEONE USE OPSWORKS
Pick one! Two tops! Make sure your entire team can understand whatever languages you go with. Avoid swapping in random new languages unless it overwhelmingly solves a problem you have better than your current languages
New open source tech comes out daily. Sometimes from cool companies we love. This doesn’t mean that its for you.
Oh? Company xyz.com released their open source fork of mongodb with a plugin to run on squirrels because it solved their scaling during a blue moon problem? This isn’t you.
Scale as you need to with an eye for where you think you might end up 6 months from now. Don’t think about 10x unless 10x is 6 months from now. If you have 10GB mysql database, you don’t need Hadoop to scale that. If you are currently ingesting 1000 data points a minute, why are you worrying about 10 million a minute?
