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 GillenAmazon Web Services and Windows Azure (Part 2)

2. CodeStock is proudly partnered with:RecruitWise and Staff with Excellence - www.recruitwise.jobsSend instant feedback on this session via Twitter:Send a direct message with the room number to @CodeStockd 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 AzureRob Gillenrob.gillenfamily.net @argodevSession 1 of 2

5. AgendaSession 1Market OverviewDiscussion of cloud primitivesSession 2Vendor-specific Lessons-LearnedGuestbook – a side-by-side code comparison

7. What HappenedIncorrect 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_anotherAmazon 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 issueDo 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 ToleranceAWSAzureRegionsAvailability ZonesElastic Load BalancingRDS in Multi-AZ modeS3/SDB/SQSMultiple InstancesRegionsGlobal Traffic ManagerSQL Azure SyncBlobs/Tables/Queues

11. Design TenantsUse independent componentsDesign everything as a black boxLoad balance and scale clustersThink about graceful degradationUse queues to isolate components

12. ApplicationExamples

13. Computer Forensics

14. Document Clustering – Dynamic ScalingRC1C2C4C3

15. Document Clustering – Dynamic ScalingRC1C2C4C3aQC1C2C3bPatent Pending

16. Document Clustering – Fault ToleranceC1C1C2C1C3C3C2C3C4C4

17. Document Clustering – Fault ToleranceC1C1C2C1C3C3C2C3C4C4

18. Document Clustering – Fault ToleranceC1C1C2C1C3C2C3C4C4

19. Document Clustering – Fault ToleranceC1C1C2C1C3C5C2C3C4C4

20. Guest Book ExampleNo-SQL StoreWeb Site1. User Written to Table2. Full-Res image written to blob store3. Generate Thumbnail task storedBlob Store4. Background service receives taskBackground Image Processing Service5. Full-Size image retrieved from storageQueue6. Thumbnail generated and written to storage7. No-SQL Store is updated with path to thumbnail

21. Questions?Rob Gillenhttp://rob.gillenfamily.net@argodevRate this talk: http://spkr8.com/t/7720Free Access:http://windowsazurepass.comCode: ROBONAZUREhttp://aws.amazon.com/free/