High Performance Web Applications

High Performance
Web Applications
Dr. Matt Wood
matthew@amazon.com
@mza

Building blocks for wonderful applications
Storage, compute, databases, managed services

Retail Merchant Web
services services

H
Getting started with
Amazon Web Services

quick review

H

Utility computing

Available at the end of an API call.
Metered billing.

H

Family of 20 services

Adding new services and reﬁnement weekly.
Rapid rate of innovation.

H

Undi!erentiated heavy lifting

Focus on your app, customers and business

H

aws.amazon.com
Free account.
Free tier.

r
Building High Performance
Web Applications

r

Deliver a great experience to
your customers.

Responsive, fast web applications.

SCALE
g DECOUPLED OUT OPTIMIZE FOR COST S

5 patterns for
performance

v
CALIBRATED FOR:

CPU performance
v
CALIBRATED FOR:

IO performan
ce
C
AUTOMATE

Assets

Application

Analytics

r

Images, javascript, stylesheets,
HTML pages

Deliver as fast as possible to customers

r

Websites without the servers

Highly durable: 99.999999999%
Zero conﬁg: ﬁre and forget

r

Low latency delivery of assets

Local caching for fast downloads
Amazon CloudFront

r

Create content distributions

From objects in S3
Any custom origin
Dynamic, streaming and static content

r

CNAME?

Map to any custom URL
assets.domain.com, www.domain.com

r

Application architecture

Small things, loosely coupled

Assets

Load balancer

App servers
Application

Database

Asynchronous processing

Analytics

r

Shared responsibility

Infrastructure by AWS
OS, application and data by customers
Tools to help meet best practices

r

Security groups

Customer controlled ﬁrewalls
All ports are closed by default

Assets

Load balancer

x App servers
Application

Database


Analytics

r

Decoupling provides an architectural
framework for performance

Easier to separate concerns: assets, streaming, etc.
Easier to manage and scale.

r

Elasticity is a tenet of the cloud

Scale up when you need to
Scale down when you don’t

r Predictable peaks
Demand

Capacity

Time

r Variable usage
Demand

Capacity

Time

r Variable usage
Demand

Time

r

Horizontal scaling
drives performance up

...and costs down

r

Amazon Machine Images
encapsulate your app

Customize your virtual machines
AMI can be the unit of deployment

r

1. Spin up a new instance
using your AMI

Conﬁgured to bootstrap the app.

r

2. Pull down latest code base

From S3 or code repository

r

3. Start up the app on the instance

Ready to receive requests

r

4. Register with the load balancer

Job done.

r

Horizontal scaling allows for
fault tolerance

Assets

Load balancer

:( App servers
Application

Database


Analytics

r

Deploying and scaling a datastore

Follow the same patterns:
horizontal scale, availability, automation.

r

One question:
Does your application require a
strict, controlled schema for query ﬂexibility?

Does your application require a strict, controlled schema
r for query ﬂexibility? Yes

Amazon Relational Database Service

Management systems: CRM, ERP, ﬁnance

r

Focus on your app

Handles tedious database admin tasks
Designed for availability

r

Multi-engine

MySQL, Oracle, Microsoft SQL Server
Up and running in six clicks

r

Point in time snapshots

Automatic. Easy recovery.

r

High availability

Deployed across multiple availability zones.
Synchronous writes.

r

Read replicas

Perfect for read heavy applications.
Asynchronous writes.
Replication metrics available.

Does your application require a strict, controlled schema
r for query ﬂexibility? No

Amazon DynamoDB

Web apps, social apps, mobile apps,
user generated content,
unstructured data integration, lots of data.

r

Focus on your app

Managed NoSQL database service.
No schema.

r

Unlimited scale

Unlimited storage
Pay as you go

r

High performance

Single digit millisecond latencies

r

Zero admin

No instances to manage
Tiny API, perfectly formed

r


Resize images. Transcode movies.
Resample media.

r

Follow the same best practices

Decouple. Stateless. Horizontal scale.

r

CloudFront for dynamic content

Edge caching for dynamic content
Cache by query string parameters
Multiple origin servers
Persistent connections to origin servers

r

Automate everything

The tedious.
The time consuming.
The error prone.

r

For example:
when increasing capacity
Launch instance.
Update application code.
Register with load balancer.

r

Auto-scaling

CloudWatch
Auto-scaling service
Elastic Load Balancer

r

Set operational thresholds

Network capacity > 80%
Memory utilization > 75%
CPU < 50%

r

Automatically respond to
operational alarms
Network capacity > 80%: add instances
Memory utilization > 75%: add instances
CPU < 50%: remove instances

r

Set bounds

Step change conﬁgured by number or
percentage of instances

r

Custom metrics

Respond to custom metrics
Page load time
Database query time

r

Automatic load balancer
conﬁguration
Instances added/removed automatically
Health check for running application before
routing tra"c

r

Stateless operations are important

Decoupled, but stateless
Instances are naive to other instances

r

Treat your data as a royal garden

Backup to S3: high durability
Compute is a disposable resource

CALIBRATED FOR:
v CPU performance

r

Range of resources

Choose the best instance type
for performance

r

t1.micro m1.small cc2.8xlarge

r

High memory High CPU + memory

t1.micro m1.small High CPU cc2.8xlarge

1 instance for 100 hours
=
100 instances for 1 hour

r

Balance cost/performance

Mix instance types for application servers,
databases, ancillary services, analytics etc.

r

Migrate to large instance types

As your application grows
Use 64 bit from the outset, if possible

CALIBRATED FOR:
v IO performance

r

IO bound web applications are
more common

Application requires predictable, consistent IO

r

Provisioned throughput with
DynamoDB
No need to provision storage
Provision IO requirements:
reads and writes per second

r

Scale up, and carry on

DynamoDB will manage resources to
achieve and maintain throughput

r

Low latency, unlimited scale

Writes acknowledged when saved to disk in
multiple data centres. Backed on SSDs.

r

hi1.4xlarge instances

High capacity, high performance storage
2 x 1Tb SSD drives

r

Perfect match for databases

Relational and NoSQL storage

r

Perfect match for databases

Relational and NoSQL storage
90k to 120k IOPS

r

High performance network

10 gigabit ethernet
Placement groups
Perfect for distributed stores

r

Economies of scale

Drive down prices for customers
20 price drops in past 6 years

r

Maximize utilization

Greater utilization drives down cost

Utilization

Reserved capacity

Time

r

Reserved instances

Small upfront payment
Guaranteed capacity for 1 or 3 years
Lower hourly rate

r

Reserved instance resale

Sell your reservations on the resale market
Sellers set your own price
Buyers select and check out

Utilization

On-demand

Reserved capacity

Time

r

Spot instances

Name your price computing

r

Spot instances

Lower costs
‘Overclock’ your app: more bang for your buck

Assets

Load balancer

App servers
Application

Database on SSDs


Analytics

r

Become price aware

Price is a driver of your architecture

r

Automated bidding

Automate bids based on on-demand price
Run on spot only when cost e!ective

r

Continuous cost optimization

Evaluate your reserved instance/on-demand/
spot mix regularly as app requirements change

g DECOUPLED

5 patterns for
performance

SCALE
g DECOUPLED OUT

5 patterns for
performance

SCALE

5 patterns for
performance

SCALE

5 patterns for
performance

CALIBRATED FOR:
v CPU performance
CALIBRATED FOR:

v IO performan
ce

Thank you
matthew@amazon.com

aws.amazon.com
@mza

High Performance Web Applications

High Performance Web Applications

Recommended

More Related Content

What's hot

What's hot(20)

Viewers also liked

Viewers also liked(20)

Similar to High Performance Web Applications

Similar to High Performance Web Applications(20)

More from Amazon Web Services

More from Amazon Web Services(20)

Recently uploaded

Recently uploaded(20)

High Performance Web Applications