This document summarizes Rob Gillen's presentation on Amazon Web Services (AWS) and Windows Azure. The presentation covers: 1. An overview of the cloud computing market and discussion of core cloud primitives. 2. Examples of fault tolerance techniques used by AWS and Azure like regions, availability zones, load balancing, and replication. 3. Lessons learned on vendor-specific implementations including an example of an incorrect network change at AWS that caused a "replication storm". 4. Examples of application architectures that leverage cloud services for dynamic scaling, fault tolerance, and background processing using independent components, load balancing, and queues.

1. Rob Gillen Amazon Web Services and Windows Azure (Part 2)

2. CodeStock is proudly partnered with: RecruitWise and Staff with Excellence - www.recruitwise.jobs Send instant feedback on this session via Twitter: Send a direct message with the room number to @CodeStock d codestock413aThis guy is AMAZING! For more information on sending feedback using Twitter while at CodeStock, please see the “CodeStock README” in your CodeStock guide.

4. Amazon Web Services and Windows Azure Rob Gillen rob.gillenfamily.net @argodev Session 1 of 2

5. Agenda Session 1 Market Overview Discussion of cloud primitives Session 2 Vendor-specific Lessons-Learned Guestbook – a side-by-side code comparison

7. What Happened Incorrect Network Change == Replication Storm for EC2 “Affected Availability Zone” Actually affected *multiple* AZs (initially) "Each availability zone runs on its own physically distinct, independent infrastructure, and is engineered to be highly reliable. Common points of failures like generators and cooling equipment are not shared across Availability Zones. Additionally, they are physically separate, such that even extremely uncommon disasters such as fires, tornados or flooding would only affect a single Availability Zone." http://aws.amazon.com/ec2/faqs/#How_isolated_are_Availability_Zones_from_one_another Amazon had a “cloud burst”

8. Oh No! The Cloud Can’t be Trusted!!! Is your data center any better? How would YOU recover from this type of issue Do you regularly TEST your HA/Recovery plans. What would it cost you to independently provide the same level of redundancy/fault-tolerance as current cloud providers offer? How do you cost-justify that compared to current cloud offerings?

10. Fault Tolerance AWS Azure Regions Availability Zones Elastic Load Balancing RDS in Multi-AZ mode S3/SDB/SQS Multiple Instances Regions Global Traffic Manager SQL Azure Sync Blobs/Tables/Queues

11. Design Tenants Use independent components Design everything as a black box Load balance and scale clusters Think about graceful degradation Use queues to isolate components

12. ApplicationExamples

13. Computer Forensics

14. Document Clustering – Dynamic Scaling R C1 C2 C4 C3

15. Document Clustering – Dynamic Scaling R C1 C2 C4 C3a QC1C2 C3b Patent Pending

16. Document Clustering – Fault Tolerance C1 C1C2 C1C3 C3 C2 C3C4 C4

17. Document Clustering – Fault Tolerance C1 C1C2 C1C3 C3 C2 C3C4 C4

18. Document Clustering – Fault Tolerance C1 C1C2 C1C3 C2 C3C4 C4

19. Document Clustering – Fault Tolerance C1 C1C2 C1C3 C5 C2 C3C4 C4

20. Guest Book Example No-SQL Store Web Site 1. User Written to Table 2. Full-Res image written to blob store 3. Generate Thumbnail task stored Blob Store 4. Background service receives task Background Image Processing Service 5. Full-Size image retrieved from storage Queue 6. Thumbnail generated and written to storage 7. No-SQL Store is updated with path to thumbnail

21. Questions? Rob Gillen http://rob.gillenfamily.net @argodev Rate this talk: http://spkr8.com/t/7720 Free Access: http://windowsazurepass.comCode: ROBONAZURE http://aws.amazon.com/free/