Developing for Your Target Market - Social, Games & Mobile - AWS India Summit 2012
•
6 likes•1,204 views
Developing for Your Target Market - Social, Games & Mobile from the AWS Summit India Startup Track
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (19)
Similar to Developing for Your Target Market - Social, Games & Mobile - AWS India Summit 2012
Similar to Developing for Your Target Market - Social, Games & Mobile - AWS India Summit 2012 (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
Developing for Your Target Market - Social, Games & Mobile - AWS India Summit 2012
- 1. Developing for your Target Market: Social, Games & Mobile Kingsley Wood AWS Business Development
- 3. Compute Storage Database Networking
- 4. 503 Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
- 5. 503 Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
- 6. Core Components Media Relational NoSQL Storage Database Database S3 RDS DynamoDB Scalability Content Compute ELB & London Distribution EC2 AutoScaling CloudFront Paris NY
- 7. Putting it all together
- 8. 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
- 9. Best Practices OFFLOAD static content • reduce your compute demand and costs • improve end-user experience • increase reliability and durability +
- 10. Best Practices WHOLE SITE via CloudFront • reduce your compute demand and costs • improve end user experience • minimize chatter and simpler model +
- 11. 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
- 13. 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
- 14. 18m users 410TB data 12 staff
- 15. $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 Hour Optimize by the time of day $15 / hr night
- 16. Best Practices DATABASE smarts • scale out and share work • optimal performance, minimize load • enhance reliability, ensure data safety • cost reduction Availability Zone Availability Zone
- 21. Best Practices A/B TEST experiment, evolve • inexpensive idea validation • seamless switch over and versioning • rapid dev / test agility
- 26. "2 backend engineers can scale a system to 30+ million users."
- 27. 1. Use multiple availability zones
- 28. 2. Use RDS with replicas and slaves
- 29. 3. Use auto-scaling groups
- 30. 4. Use Elastic Load Balancing
- 31. 5. Use CloudFront and Route53 at the edge
- 32. Questions? Kingsley Wood AWS Business Development
Editor's Notes
- 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