This document summarizes a presentation about sampling different cloud computing options. It defines key concepts like private vs public clouds, infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS). The presentation discusses considering an application's computing, storage, reach, and value requirements when choosing a cloud provider. It provides examples of different cloud platforms and services. The goal is to help people understand the "cloud smörgåsbord" or variety of options available.

1. Sampling the Cloud Smörgåsbord Presented at Vermont Code Camp September 10, 2011 Jim O’NeilDeveloper Evangelist, Microsoftjim.oneil@microsoft.com @jimoneil

2. The Law of Two Feet

3. This talk is not about…

4. And it’s not about…

5. or

6. There are no sexy demos...

8. Finally, it’s not about…

9. THIS is what it’s about

10. There is nothing permanent except change Heraclitus of Ephesus ca. 6th century BC

11. NIST’s Taxonomy Private Cloud Deployment Models Community Cloud Public Cloud Hybrid Cloud Essential Characteristics Infrastructure as a Service Rapid Elasticity Broad network access Platform as a Service Service Models Software as a Service Resource Pooling On-demand self-service Measured service

12. Some of the Players PaaS com SaaS AppHarbor IaaS

13. What do you need from the Cloud? compute storage reach value

14. What do you need from the Cloud? compute storage reach value

15. Compute Generally virtualization based IAAS: build your VM and they’ll run it PAAS: build your app and they’ll run it (on a VM) Several flavors across vendors Web requests (in and out) “Worker” requests (long running) High-performance compute Local emulation

16. Compute Survey app engine

17. Developer Support app engine

18. What do you need from the Cloud? compute storage reach value

19. Storage One size does not fit all…. * Consistency varies among implementations, Windows Azure is strongly consistent; many others are eventually consistent; some are both.

20. Storage Sampler app engine

21. What do you need from the Cloud? compute storage reach value

22. Reach: Where The trinity of reach Where are your users? Where is your app? Where is your data? Latency Data and application co-location Multiple data centers = multiple service points Content Delivery Network (CDN) Availability [Auto] scaling capabilities Geo-distribution Disaster recovery: Multiple data centers/providers Compliance

23. Reach: Where app engine 1IkaiLan, Google, Aug. 2, 2011 - http://bit.ly/qvrm6W

24. Reach: How Identity Anonymous Authenticated Federated Connectivity options B2B (“behind the firewall”) Hybridization of on-premises and cloud assets Geo-distribution

25. Reach: How app engine

26. What do you need from the Cloud? compute storage reach value

27. Value Cost Structure “Freemium” Metered service usage Per application/per user Subscription based Service Level Agreements Generally none at the “Freemium” level Usually some at the paid levels (generally commensurate with the plan)

28. More to Think About! Management Monitoring (automatic and manual) Billing Compliance SSAE 16 (SAS 70) PCI HIPAA FISMA ISO 27001SOX EU Data Protection Directive Other services MapReduce (e.g., Hadoop) BI in the cloud (e.g., Windows Azure Reporting Services) E-mail (e.g., Sendgrid) Payment services (e.g., Amazon DevPay) Marketplaces (e.g., Windows Azure Marketplace)

29. So, are you here?

30. Or here?

32. Thank You & Bon Appetit! Jim O’NeilDeveloper Evangelist, Microsoftjim.oneil@microsoft.com @jimoneil