The document provides an overview of cloud computing, detailing various types such as Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS), along with their benefits and risks. It emphasizes the shift towards cloud solutions for flexibility and control, while also highlighting privacy and security concerns associated with these services. Additionally, it notes the revival of Independent Software Vendors (ISVs) due to cloud technology enabling non-IT managers to deploy applications without heavy capital investment.

1. An Overview of Cloud ComputingChristopher Curtin

2. About Me19+ years in TechnologyBackground in Factory Automation, Warehouse Management and Food Safety system development before SilverpopCTO of SilverpopSilverpop is a leading marketing automation and email marketing company

3. Cloud ComputingWhat exactly is ‘cloud computing’?Beats meMost overused term since ‘dot com’Ask 10 people, get 11 answers

4. TopicsTypes of CloudsInfrastructure as a Service (IaaS)Platform as a Service (PaaS)Software as a Service (SaaS)PrivateHybridGoogle DocsPrivacy and securityReturn of the ISV?Map Reduce/HadoopThoughts for Architects

5. Infrastructure as a Service (IaaS)Provides ‘raw iron’ VM for you to usePretty much a root login and total control‘pay as you go’ – charged by hour running and bandwidth/storage usedAmazon’s EC2 Rackspace CloudProbably every co-lo provider

6. IaaS Benefits and RisksBenefitsDo whatever you want on the machineBuild it however you want‘pay as you go’Can deploy one server or 1000RisksSame as benefitsMostly credit card todayNot something you’d give to a business groupAuthentication is not provided

7. IaaS – EC2Offers prebuildmachine images ‘AMI’Can build your own as wellProvides some infrastructure services such as load balancing, basic monitoring, queuing, disk storageBiggest design challenge - storage

8. Platform as a Service (PaaS)Platforms provide you a container and set of servicesYou code to the API, worrying about business logic, not infrastructureMicrosoft’s AzureGoogle’s AppEngineSalesForce.com’s Force.comEngineYard for Ruby

9. PaaSVery well defined ‘boxes’ to work inEven when .net and Java containers are provided, not all APIs and libraries are availableNo local diskHard (impossible?) to know how many instances are running

10. PaaS Benefits and RisksBenefitsNo need to worry about networking, load balancers, Apache/IIS etcAuto scaling is part of the applicationRisksSame as BenefitsAuthentication is not robustConstraints Credit Card payments

11. PaaS – Azure and AppEngineBasically provide Servlet/MVC containersAzure provides SQL ServerAppEngine provides JDO access to BigTable-like databaseLong running tasks not supported (how to do reporting?)No third party libraries, applications etc to integrate into your solution

12. Software as a Service (SaaS)Traditional Web applications?Business applications hosted by othersSilverpopSalesForce.comGoogle DocsMicrosoft Live

13. SaaS Benefits and RisksBenefitsNo IT costsDepartment Level managementSupport by VendorRisksPossibly no IT knowledgePrivacy, Security, data outside firewallIntegration challenges

14. SaaS Example: SilverpopProvide Lead Management and Marketing applicationsMarketing Departments lead RFP process, rarely see ITHowever, security is criticalIntegrations are often ‘build and forget’

15. Private CloudsAnother really abused termNOT the same as virtualizationAllows IaaS and PaaS inside your firewall or in a controlled, dedicated third partyEucalyptus3TeraIBM, Unisys, Sun, HP etcExpect VMWare (SpringSource)

16. Private Clouds Benefits and RisksBenefitsTotal controlProvisioningReuse of existing capital systemsEasier integrationsRisksNot adopting ‘services’ part of solutionCapital costs over time

17. Private Clouds – 3TeraTool to let you define machines as resourcesBuild ‘applications’ drag and drop Cloud can be internal, remote or both

18. 3Tera Screenshot

19. HybridsAmazon Virtual Private Cloud3TeraCloud BurstingBuild internal system for ‘normal’ loadCall up cloud resources for extreme casesDesign architectures where some parts are in the cloud and some local by default

20. Cloud Bursting ExamplesIBM DB2 Workgroup for $3/hourWhat could you do with 100 DB2 instances?BillingDay to day use local appsSpin up 100 EC2 instances to do a monthly billing runFinancialSpin up 100 EC2 instances to close the books monthlyDevelopmentLarge unit test suitesSpin up 10 EC2 instances, parallel tests nightly

21. Google DocsMicrosoft Live too (eventually)Can be PaaS or SaaSOnline collaboration Can also build simple applications (forms)

22. Privacy and SecurityIaaSAlmost none by defaultYou must build it/manage itPaaSSome by platform but often tied to Live ID, Gmail login etcSOME support integration with LDAP/Active DirectoryCritical to get this under control!

23. Privacy and Security 2SaaSAudit the vendorsPenetration testsIP restrictionsDefine rules for use of all 3Amazon Virtual Private Cloud“on your network”Can use your infrastructureSupposedly 100% VLAN’d

24. Return of the ISV?Remember the late 80’s and early 90’s?The guy from church or neighbor build dBase 3 apps for everyone?Corporate IT killed that by taking control of the desktopPaaS and SaaS will bring them back

25. ISV ContinuedIf IT is seen as the bottleneck, users will go around youAccess/Excel appsA department manager could pay someone to build an app and host it on Azure for a few thousandPaid monthly on a credit card, no capital, no IT traceability

26. Map Reduce/HadoopEver wonder how Google indexes the web?Map/Reduce is a framework for diving jobs into manageable piecesThen implementing the logic across many machines

27. Map/Reduce 2First step is to define the key for the dataFor example, words in a documentOr customer identifiersNext step is to run logic on the rows that match each key (Reduce)Output is then combined into results directory

28. Runtime Distribution © Concurrent 2009

29. Map/Reduce 3Don’t think about threading, scheduling, memory utilizationThink about business logicVERY different way of thinking about solving a problemA whole presentation by itself …

30. Product ArchitectsHow would I build my solution if I had lots of hardware on demand?What are the things we do infrequently but have dedicated hardware for?Learn about map/reduce for reporting, billing etc.

31. Product Company Architect (SaaS)What things are we doing in ‘back office’ that we only need once a week/month?What quick/dirty things are the non-production teams doing to do their jobs?Do I have the volume to support building my own infrastructure?

32. Enterprise ArchitectsKnow that your departments are going to the cloud with or without youLook at applicable use of all types of ‘cloud’ solutions: PaaS, IaaS, SaaS all have their placeThink about internal/private clouds to make resource management easierProvide resources to answer/direct departments about PaaS/SaaS

33. AWSome AtlantaMeets Second Tuesday of the month at ATDCStarted about Amazon’s services, but more general nowhttp://www.meetup.com/awsomeatlanta/

34. Thank youChris Curtin ccurtin@silverpop.comTwitter: @ChrisCurtinSlideShare: www.slideshare.com/chriscurtinSilverpop: http://www.silverpop.com/marketing-company/careers/index.html