Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Developing for Your Target Market - Social, Games & Mobile - AWS India Summit 2012

809
views

Published on

Developing for Your Target Market - Social, Games & Mobile from the AWS Summit India Startup Track

Developing for Your Target Market - Social, Games & Mobile from the AWS Summit India Startup Track

Published in: Technology

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
809
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The comfort you gain from knowing that your users won't be presented with messages such as 503 response codes mean you can sleep easy.
  • Build websites that sleep at night. Build machines only live when you need it
  • Transcript

    • 1. Developing for yourTarget Market: Social, Games & Mobile Kingsley Wood AWS Business Development
    • 2. Compute StorageDatabase Networking
    • 3. 503Service Temporarily Unavailable The server is temporarily unable to service your request due tomaintenance downtime or capacityproblems. Please try again later.
    • 4. 503Service Temporarily Unavailable The server is temporarily unable to service your request due tomaintenance downtime or capacityproblems. Please try again later.
    • 5. Core Components Media Relational NoSQL Storage Database Database S3 RDS DynamoDB Scalability Content Compute ELB & London Distribution EC2 AutoScaling CloudFront Paris NY
    • 6. Putting it all together
    • 7. Must-know best practices• OFFLOAD static content• CACHE at the edge (static and dynamic)• DRY (don’t repeat yourself)• LOAD BALANCE from the start• AUTO SCALING done right• DATABASE smarts• A/B TEST and templatize
    • 8. Best Practices OFFLOAD static content • reduce your compute demand and costs • improve end-user experience • increase reliability and durability +
    • 9. Best Practices WHOLE SITE via CloudFront • reduce your compute demand and costs • improve end user experience • minimize chatter and simpler model +
    • 10. Best Practices DRY (don’t repeat yourself) • original vs. derived assets : 33% savings • single reference and consistency • control, accurate logs and tracking S3 (or Glacier) RRS
    • 11. Best Practices LOAD BALANCE from the start • ready for massive scale, high reliability • uninterrupted growth and evolution • stateless and redundant array Availability Zone Availability Zone
    • 12. 18m users 410TB data 12 staff
    • 13. $52 / hr day 14 Daily CPU Load 12 10 8 Load 6 Big Savings 4 2 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 HourOptimize by the time of day $15 / hr night
    • 14. Best Practices DATABASE smarts • scale out and share work • optimal performance, minimize load • enhance reliability, ensure data safety • cost reduction Availability Zone Availability Zone
    • 15. Best Practices A/B TEST experiment, evolve • inexpensive idea validation • seamless switch over and versioning • rapid dev / test agility
    • 16. "2 backend engineers can scalea system to 30+ million users."
    • 17. 1. Use multiple availability zones
    • 18. 2. Use RDS with replicas and slaves
    • 19. 3. Use auto-scaling groups
    • 20. 4. Use Elastic Load Balancing
    • 21. 5. Use CloudFront and Route53 at the edge
    • 22. Questions? Kingsley WoodAWS Business Development