Build a Website & Mobile App for your first 10 million users

© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Build a Website & Mobile App
on AWS for Your First 10
Million Users

© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Build a Website on AWS for Your First
10 Million Users11

Who are you?

http://i.telegraph.co.uk/multimedia/archive/02674/CLIMBER_2674482b.jpg

Now that’s a lot
of things to read!
This is NOT
where we
want to start!

It’s not the single thing that
fixes everything.

What do we need first?

Some basics…

AWS Global Infrastructure
Region, # of zones
Coming Soon!

AWS Global Infrastructure
Region, # of zones
Coming Soon!
90+ Edge
Locations

Global Footprint
190 countries
2,300 government agencies
7,000 educational institutions
22,000 Non profits organizations
16 regions (4 more announced)
43 availability zones
76 edge locations
AWS regions consists of multiple Availability Zones (“AZs”) isolated for failures and with low latency networks
connectivity making AWS the only provider that allows HA natively supported
Region & Number of Availability Zones
AWS GovCloud (2)
US West: Oregon (3), Northern California (3)
US East: Northern Virginia (5), Ohio (3)
Canada: Central (2)
South America: São Paulo (3)
Europe: Ireland (3), Frankfurt (3), London (2)
Asia Pacific: Singapore (2), Sydney (3), Tokyo (3), Seoul (2), Mumbai (2)
China: Beijing (2)
New Region (coming soon): Paris, Ningxia, Stockholm, Hong Kong

ENTERPRISE
APPS
DEVELOPMENT & OPERATIONSMOBILE SERVICESAPP SERVICESANALYTICS
Data
Warehousing
Hadoop/
Spark
Streaming Data
Collection
Machine
Learning
Elastic
Search
Virtual
Desktops
Sharing &
Collaboration
Corporate
Email
Backup
Queuing &
Notifications
Workflow
Search
Email
Transcoding
One-click App
Deployment
Identity
Sync
Single Integrated
Console
Push
Notifications
DevOps Resource
Management
Application Lifecycle
Management
Containers
Triggers
Resource
Templates
TECHNICAL &
BUSINESS
SUPPORT
Account
Management
Support
Professional
Services
Training &
Certification
Security
& Pricing
Reports
Partner
Ecosystem
Solutions
Architects
MARKETPLACE
Business
Apps
Business
Intelligence
Databases
DevOps
Tools
NetworkingSecurity Storage
Regions
Availability
Zones
Points of
Presence
INFRASTRUCTURE
CORE SERVICES
Compute
VMs, Auto-scaling,
& Load Balancing
Storage
Object, Blocks,
Archival, Import/Export
Databases
Relational, NoSQL,
Caching, Migration
Networking
VPC, DX, DNS
CDN
Access
Control
Identity
Management
Key
Management
& Storage
Monitoring
& Logs
Assessment
and reporting
Resource &
Usage Auditing
SECURITY & COMPLIANCE
Configuration
Compliance
Web application
firewall
HYBRID
ARCHITECTURE
Data
Backups
Integrated
App
Deployments
Direct
Connect
Identity
Federation
Integrated
Resource
Management
Integrated
Networking
API
Gateway
IoT
Rules
Engine
Device
Shadows
Device
SDKs
Registry
Device
Gateway
Streaming Data
Analysis
Business
Intelligence
Mobile
Analytics

Aws building blocks

Region
Region
Production applications that are highly available
The AWS Cloud infrastructure:
• Availability Zones (43) consist of one or more discrete data
centers, each with redundant power, networking, and
connectivity, housed in separate facilities.
• A Region (16) is a physical location in the world where we
have multiple Availability Zones.
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
21
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
AZ
Availability Zones (AZs) provide the resiliency of
performing real-time data replication and the reliability of
multiple physical locations
2
Low latency
ensures real
data replication
Distance
ensures
high
availability

So let’s start from…

You

1 User
Amazon
EC2
instance
Elastic IP
User
Amazon
Route 53

“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
c4.8xlarge
m4.2xlarge
t2.micro

1 User
• No failover
• No redundancy
• Too many eggs in one
basket
EC2
Instance
Elastic IP
User
Amazon
Route 53

Users >1

Users > 1
Web
Instance
Database
Instance
Elastic IP
User
Amazon
Route 53

Self-managed Fully managed
Amazon EC2 Amazon
DynamoDB
Amazon RDS Amazon
Redshift
Database options

• MySQL or Postgres compatible
• Automatic storage scaling (up to 64 TB)
• Up to 15 read-replicas
• Continuous (incremental) backups to
Amazon S3
• 6-way replication across 3 zones
Amazon Aurora

To NoSQL, or not to NoSQL?

Start with SQL databases

Why start with SQL?
• Established and well-worn technology.
• Lots of existing code, communities, books, and tools.
• You aren’t going to break SQL DBs in your first millions
of users. No, really, you won’t.*
• Clear patterns to scalability.
*Unless you are doing something SUPER peculiar with the data or you have MASSIVE amounts of it.
…but even then SQL will have a place in your stack.

> 5 TB in year one?
Incredibly data intensive workload?
OK!
You might need NoSQL.

Why else might you need NoSQL?
• Super low-latency applications
• Highly nonrelational data
• Need schema-less data constructs*
• Rapid ingest of data (thousands of records/sec)
• Massive amounts of data (again, in the TB range)
*Need!= “It’s easier to do dev without schemas”

Users >100

Users >100
Web
instance
Elastic IP
RDS DB
instance
User
Amazon
Route 53

Users >1000

Users >1000
Web
Instance
RDS DB Instance
Active (Multi-AZ)
Availability Zone Availability Zone
Web
Instance
RDS DB Instance
Standby (Multi-AZ)
Load
balancer
User
Amazon
Route 53

Elastic Load Balancing
• Highly available
• TCP/{1 – 65535}
• Health checks
• Session stickiness
• Monitoring / logging
• Secure sockets layer

Application Load Balancer
• Highly available
• TCP/{1 – 65535}
• Health checks
• Session stickiness
• Monitoring / logging
• Content-based routing
• Container-based apps
• WebSockets
• HTTP/2

horizontally
vertically

ASEAN Customer

Users >100,000

Users > 10,000s–100,000s
RDS DB Instance
Active (Multi-AZ)
Availability Zone Availability Zone
RDS DB Instance
Standby (Multi-AZ)
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 53User

What about
performance and efficiency?

RDS DB Instance
Active (Multi-AZ)
Availability Zone
Load
balancer
Amazon S3
Amazon
CloudFront
Amazon
Route 53
User
Shift some load around
Web Instances
Availability Zone
Web Instances
RDS DB Instance
Standby (Multi-AZ)

Load
balancer
Amazon S3
Amazon
CloudFront
Amazon
Route 53
User
Availability Zone
Web Instances
RDS DB Instance
Standby (Multi-AZ)

• Object-based storage
• Highly durable
• Great for static assets
• “Infinitely scalable”
• Objects up to 5 TB in
size
• Optional encryption
Amazon Simple Storage Service (S3)

Cache content for faster delivery
• Lower load on origin
• Dynamic and static content
• Low TTLs (as short as 0
seconds)
• Streaming video
• Custom SSL certificates
• Optimized for AWS
Amazon CloudFront

Amazon CloudFront
Response Time
Server Load
Response
Time
Server
Load
Response
Time
Server
Load
No CDN CDN for Static
Content
CDN for Static &
Dynamic Content
0
50
100
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
12:00AM
VolumeofData
Delivered(Gbps)

RDS DB Instance
Active (Multi-AZ)
Availability Zone
Load
balancer
Amazon S3
Amazon
CloudFrontUser
ElastiCache DynamoDB
Web Instances
Amazon
Route 53

Amazon DynamoDB
• Managed NoSQL database
• Provisioned throughput
• Fast, predictable performance
• Fully distributed, fault tolerant
• JSON support
• Items up to 400 KB

Amazon ElastiCache
• Managed Memcached or Redis
• Scale from one to many nodes
• Self-healing (replaces dead instance)
• Single digit ms speeds (usually)
• Local to a single AZ for Memcache
• Multi-AZ possible with Redis

RDS DB Instance
Active (Multi-AZ)
Availability Zone
Load
balancer
Amazon S3
Amazon
CloudFront
Amazon
Route 53
User
ElastiCache DynamoDB
Web Instances

Now that our web tier is
much more lightweight,
we can revisit the beginning
of our talk…

Auto Scaling!

Automatic resizing of compute clusters
Define min/max pool sizes
CloudWatch metrics drive scaling
On-Demand or Spot Instances
aws autoscaling create-auto-scaling-group
--auto-scaling-group-name MyGroup
--launch-configuration-name MyConfig
--min-size 4
--max-size 200
--availability-zones us-west-2c, us-west-2b
Auto Scaling

Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Typical weekly traffic to Amazon.com

Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Typical weekly traffic to Amazon.com
Provisioned capacity

November
November traffic to Amazon.com

November

76%
24%
November

November

Auto Scaling
lets you do this!

Users > 500,000+
Availability Zone
Amazon
Route 53
User
Amazon S3
Amazon
CloudFront
Availability Zone
Load
balancer
DynamoDB
RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
ElastiCache RDS DB Instance
Read Replica
Web
Instance
Web
Instance
Web
Instance
ElastiCacheRDS DB Instance
Standby (Multi-AZ)
RDS DB Instance
Active (Multi-AZ)

Use automation

Whoa!

AWS application management solutions
Convenience Control
Higher-level services Do it yourself
AWS
Elastic Beanstalk
AWS
OpsWorks
AWS
CloudFormation
Amazon EC2

AWS CodeDeploy
• Deploys your code to a “fleet” of EC2 instances
• 1 – 10,000s of instances
• Automatically schedules updates (multiple zones)
• Application and Deployment groups described in
YAML-formatted files
• Can reference Auto Scaling groups
• AWS Management Console, CLI, or APIs
• Can be used with Chef recipes or Puppet scripts

Users >500,000+
• Monitoring, metrics, and logging
• If you can’t build it internally,
outsource it! (third-party SaaS)
• What are customers saying?
• Try to squeeze as much performance
out of each service/component

AGGREGATE
LEVEL
METRICS
LOG
ANALYSIS
EXTERNAL
SITE
PERFORMANCE
HOST
LEVEL
METRICS

There are further
improvements to be made in
breaking apart our
web/app layer

SOA
What does this mean?

This is NOT
where we
want to start!
This IS where
we want to start!
Now that’s a lot
of things to read!

SOAing
Move services into their own tiers
• Treat them separately
• Scale them independently
It offers flexibility and greater
understanding of each component

Loose coupling + SOA = winning
DON’T REINVENT THE WHEEL
• Email
• Queuing
• Transcoding
• Search
• Databases
• Monitoring
• Metrics
• Logging
• Compute
Amazon
CloudSearch
Amazon SQSAmazon SNS
Amazon Elastic
Transcoder
Amazon SWFAmazon SES
AWS Lambda

• Reliable (Multi-AZ)
• Scalable (unlimited messages)
• Secure (queue authentication)
• Simple (simple APIs)
Application Services – Amazon SQS
SQS
messages
Get
message
Instance
Put
message
Instance
Amazon SNS Topic
Publish
notification
Queue is subscribed
to topic

Compute / Platform – AWS Lambda
• Functions triggered by events
• JavaScript, Java, Python, and C#
• Managed
• Implicit scaling
S3 bucket
Lambda
Push: event
notification
DynamoDB
Pull: DynamoDB
Stream
Amazon
Kinesis
Pull:
Amazon Kinesis
stream

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
• Don’t build your own!
S3 bucket
Lambda
Push: event
notification
DynamoDB
Pull: DynamoDB
Stream
Amazon
Kinesis
SQS
messages
Get
message
Instance
Put
message
Instance
Amazon SNS Topic
Publish
notification
Queue is subscribed
to topic
Pull:
Amazon Kinesis
stream

Users >1,000,000

Users >1 million+
Reaching a million and above is going to require some bit
of all the previous things:
• Multi-AZ
• Elastic Load Balancing between tiers
• Auto Scaling
• Service oriented architecture (SOA)
• Serving content smartly (Amazon S3/CloudFront)
• Caching off DB
• Moving state off tiers that auto scale

Users >1 million+
RDS DB Instance
Active (Multi-AZ)
Availability Zone
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
Lambda

Global Customer

The next big steps

Users >5 million - 10 million
Database Issues?
How can you solve it?
• Federation—splitting into multiple DBs based on function
• Sharding—splitting one dataset up across multiple hosts
• Moving some functionality to other types of DBs (NoSQL, Graph)

Database federation
• Split up databases by function/purpose
• Harder to do cross-function queries
• Essentially delays sharding/NoSQL
• Won’t help with single huge functions/tables
Forums DB
Users DB
Products
DB

Sharded horizontal scaling
• More complex at the application layer
• No practical limit on scalability
• Operation complexity/sophistication
• Shard by function or key space
• RDBMS or NoSQL
User ShardID
002345 A
002346 B
002347 C
002348 B
002349 A
CBA

Shifting functionality to NoSQL
• Similar in a sense to federation
• NoSQL vs. SQL
• Leverage managed services like
DynamoDB
Some use cases:
• Leaderboards/scoring
• Rapid ingest of clickstream/log data
• Temporary data needs (cart data)
• “Hot” tables
• Metadata/lookup tables
DynamoDB

A quick review

A quick review
• Multi-AZ your infrastructure.
• Make use of self-scaling services—ELB, Amazon S3,
Amazon SNS, Amazon SQS, Amazon SWF, Amazon SES, etc.
• Built-in redundancy at every level
• Start with what you know: SQL/NoSQL
• Cache data both inside and outside your infrastructure.
• Use automation tools in your infrastructure.

A quick review continued
• Make sure you have good metrics/monitoring/logging
• Split tiers into individual services (SOA)
• Use Auto Scaling once you’re ready for it
• Don’t reinvent the wheel
• Move to NoSQL if and when it makes sense

Web and Mobile Application for
11 Million Users

Follow Us on Social Media
@AmazonWebServices
@AWSCloud @AWSCloudSEAsia

Thank You

Build a Website & Mobile App for your first 10 million users

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Build a Website & Mobile App for your first 10 million users

Similaire à Build a Website & Mobile App for your first 10 million users (20)

Plus de Amazon Web Services

Plus de Amazon Web Services (20)

Build a Website & Mobile App for your first 10 million users