This document discusses architectural principles for building scalable and resilient applications on AWS. It emphasizes elasticity, loose coupling between services, high availability through redundancy and automation, and agility through infrastructure as code. Specific AWS services are recommended for implementing these principles, such as S3, DynamoDB, SQS, SWF, and CloudFormation. Architecting applications on AWS requires thinking about the entire architecture rather than just the application code.

1. Architecting your
Killer App on AWS
Evangelist Amazon Web Services
zieglerj@amazon.com
@jiyosub

2. Standing on the Shoulders of Giants

3. Elasticity
Loose Coupling
High Availability
Agility

4. Elasticity
Loose Coupling
High Availability
Agility

5. Elasticity
On and Off Fast Growth
Variable peaks Predictable peaks

6. Elasticity
On and Off WASTE Fast Growth
Poor
Variable peaks Service Predictable peaks

7. Elasticity
On and Off Fast Growth
Variable peaks Predictable peaks

8. Animoto
Capacity
Peak of 5,000
EC2 instances
Launch of
Facebook App
Time

9. I’m sold,
how do I get it?
You have to be able
to scale horizontally!

10. Scale Horizontally
Stateless Compute
More Servers = More Power
Bootstrapping is your Friend

13. Design Techniques
Develop with Load Balancer
State into NoSQL or cache
Automate
Bootstrap from S3

14. Elasticity
Loose Coupling
High Availability
Agility

15. Loose Coupling
The looser they are coupled,
the bigger they scale.

16. Upload Analysis Rendering Distribution

17. Sounds good, I’ll
take some Loose Coupling too
Focus on Services
Simple Queuing Service
Scale Services Horizontally
Autoscale on Queue Size

18. TRANSCODE
RECEIVE
& PUBLISH
QUEUE

19. AMAZON SWF
WORKFLOW SERVICE FOR SCALABLE,
RESILIENT APPLICATIONS

20. TASK GRAPH
WITH DECISIONS?
GOOD OK
RECEIVE CHECK SPAM
TRANSCODE
VIDEO LENGTH CHECK
LONG SPAM
SHORTEN PUBLISH
REJECT
VIDEO & NOTIFY
use AMAZON SWF

21. CHAINED TASKS
WITHOUT DECISIONS?
RECEIVE TRANSCODE NOTIFY
use AMAZON SQS

22. Elasticity
Loose Coupling
High Availability
Agility

23. High Availability
Avoid single points of failure.
Assume everything fails, and design
backwards.

24. High Availability
Avoid single points of failure
Assume everything fails, and design
backwards

25. AWS BUILDING
BLOCKS
Inherently Fault-Tolerant Fault-Tolerant
Services with the right
 Amazon S3  Amazon Route53 architecture
 Amazon  Elastic Load  Amazon EC2
SimpleDB Balancing
 Amazon EBS
 Amazon  AWS IAM
 Amazon RDS
DynamoDB
 AWS Elastic
 Amazon VPC
 Amazon Beanstalk
CloudFront
 Amazon
 Amazon SWF ElastiCache
 Amazon SQS  Amazon EMR
 Amazon SNS  Amazon
CloudSearch
 Amazon SES

26. Highly
Available State
Consider S3 for Read Access
Partition Data
Reduce Reliance on Relational
Database Systems

27. Highly Available
Deployment
Route 53
Build and Destroy
Hot Standby

30. Design for Failure

31. Elasticity
Loose Coupling
High Availability
Agility

32. Focus on Core
Competencies
Database Scaling
Search
Scalable Web Properties
Email Services

33. Infrastructure
as Code
“Programmatic
provisioning by API”
Everything in AWS is an API

34. Tool Box
A
M Libraries and SDKs
I
AMI
CloudFormation

35. Agile Architecture

36. Change the
Paradigm
“You are no longer writing an application.
You are creating an entire architecture”

37. Elasticity
Loose Coupling
High Availability
Agility