Architecting yourKiller App on AWS   Evangelist Amazon Web Services       zieglerj@amazon.com               @jiyosub
Standing on the Shoulders of Giants
ElasticityLoose CouplingHigh Availability    Agility
ElasticityLoose CouplingHigh Availability    Agility
ElasticityOn and Off               Fast GrowthVariable peaks           Predictable peaks
ElasticityOn and Off         WASTE Fast Growth                  PoorVariable peaks    Service   Predictable peaks
ElasticityOn and Off              Fast GrowthVariable peaks          Predictable peaks
AnimotoCapacity                       Peak of 5,000                       EC2 instances           Launch of           Face...
I’m sold, how do I get it? You have to be ableto scale horizontally!
Scale Horizontally    Stateless ComputeMore Servers = More PowerBootstrapping is your Friend
Design TechniquesDevelop with Load Balancer State into NoSQL or cache          Automate     Bootstrap from S3
ElasticityLoose CouplingHigh Availability    Agility
Loose CouplingThe looser they are coupled,   the bigger they scale.
Upload   Analysis   Rendering   Distribution
Sounds good, I’lltake some Loose Coupling too       Focus on Services    Simple Queuing Service   Scale Services Horizonta...
TRANSCODERECEIVE                   & PUBLISH          QUEUE
AMAZON SWFWORKFLOW SERVICE FOR SCALABLE,    RESILIENT APPLICATIONS
TASK GRAPH          WITH DECISIONS?                        GOOD              OKRECEIVE         CHECK          SPAM        ...
CHAINED TASKS WITHOUT DECISIONS?RECEIVE   TRANSCODE   NOTIFYuse AMAZON SQS
ElasticityLoose CouplingHigh Availability    Agility
High AvailabilityAvoid single points of failure.Assume everything fails, and designbackwards.
High AvailabilityAvoid single points of failureAssume everything fails, and designbackwards
AWS BUILDING                  BLOCKS  Inherently Fault-Tolerant             Fault-Tolerant          Services              ...
Highly     Available State Consider S3 for Read Access       Partition DataReduce Reliance on Relational     Database Syst...
Highly Available  Deployment    Route 53Build and Destroy  Hot Standby
Design for Failure
ElasticityLoose CouplingHigh Availability    Agility
Focus on Core   Competencies    Database Scaling         SearchScalable Web Properties     Email Services
Infrastructure          as Code       “Programmatic     provisioning by API”Everything in AWS is an API
Tool Box                  A                  M         Libraries and SDKs                   I                  AMICloudFor...
Agile Architecture
Change the               Paradigm“You are no longer writing an application. You are creating an entire architecture”
ElasticityLoose CouplingHigh Availability    Agility
Architecting Your Killer App on AWS - AWS India Summit 2012
Architecting Your Killer App on AWS - AWS India Summit 2012
Architecting Your Killer App on AWS - AWS India Summit 2012
Architecting Your Killer App on AWS - AWS India Summit 2012
Upcoming SlideShare
Loading in …5
×

Architecting Your Killer App on AWS - AWS India Summit 2012

1,098
-1

Published on

Architecting Your Killer App on AWS from the AWS Summit in India Startup Track

Published in: Technology
0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,098
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
41
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide
  • Autoscale on Queue Length
  • StateExecuted tasksTimeoutsErrors
  • 00:47:00
  • Architecting Your Killer App on AWS - AWS India Summit 2012

    1. 1. Architecting yourKiller App on AWS Evangelist Amazon Web Services zieglerj@amazon.com @jiyosub
    2. 2. Standing on the Shoulders of Giants
    3. 3. ElasticityLoose CouplingHigh Availability Agility
    4. 4. ElasticityLoose CouplingHigh Availability Agility
    5. 5. ElasticityOn and Off Fast GrowthVariable peaks Predictable peaks
    6. 6. ElasticityOn and Off WASTE Fast Growth PoorVariable peaks Service Predictable peaks
    7. 7. ElasticityOn and Off Fast GrowthVariable peaks Predictable peaks
    8. 8. AnimotoCapacity Peak of 5,000 EC2 instances Launch of Facebook App Time
    9. 9. I’m sold, how do I get it? You have to be ableto scale horizontally!
    10. 10. Scale Horizontally Stateless ComputeMore Servers = More PowerBootstrapping is your Friend
    11. 11. Design TechniquesDevelop with Load Balancer State into NoSQL or cache Automate Bootstrap from S3
    12. 12. ElasticityLoose CouplingHigh Availability Agility
    13. 13. Loose CouplingThe looser they are coupled, the bigger they scale.
    14. 14. Upload Analysis Rendering Distribution
    15. 15. Sounds good, I’lltake some Loose Coupling too Focus on Services Simple Queuing Service Scale Services Horizontally Autoscale on Queue Size
    16. 16. TRANSCODERECEIVE & PUBLISH QUEUE
    17. 17. AMAZON SWFWORKFLOW SERVICE FOR SCALABLE, RESILIENT APPLICATIONS
    18. 18. TASK GRAPH WITH DECISIONS? GOOD OKRECEIVE CHECK SPAM TRANSCODE VIDEO LENGTH CHECK LONG SPAM SHORTEN PUBLISH REJECT VIDEO & NOTIFYuse AMAZON SWF
    19. 19. CHAINED TASKS WITHOUT DECISIONS?RECEIVE TRANSCODE NOTIFYuse AMAZON SQS
    20. 20. ElasticityLoose CouplingHigh Availability Agility
    21. 21. High AvailabilityAvoid single points of failure.Assume everything fails, and designbackwards.
    22. 22. High AvailabilityAvoid single points of failureAssume everything fails, and designbackwards
    23. 23. 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
    24. 24. Highly Available State Consider S3 for Read Access Partition DataReduce Reliance on Relational Database Systems
    25. 25. Highly Available Deployment Route 53Build and Destroy Hot Standby
    26. 26. Design for Failure
    27. 27. ElasticityLoose CouplingHigh Availability Agility
    28. 28. Focus on Core Competencies Database Scaling SearchScalable Web Properties Email Services
    29. 29. Infrastructure as Code “Programmatic provisioning by API”Everything in AWS is an API
    30. 30. Tool Box A M Libraries and SDKs I AMICloudFormation
    31. 31. Agile Architecture
    32. 32. Change the Paradigm“You are no longer writing an application. You are creating an entire architecture”
    33. 33. ElasticityLoose CouplingHigh Availability Agility
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×