Cloud Computing 101


Published on

Presentation given by Ben Kepes to the New Zealand Cloud Computing Summit

Published in: Technology, Business
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Agenda for today
  • A very quick introduction to what cloud computing actually is…
  • A very quick introduction to what cloud computing actually is…
  • Some common themes of cloud computing
  • Another visual explanation
  • Cloud computing paradigm of computing in which dynamically scalable and often virtualized resources are provided as a service over the InternetUsers need not have knowledge of, expertise in, or control over the technology infrastructure in the "cloud" that supports themThe concept generally incorporates combinations of the following:infrastructure as a service (IaaS)platform as a service (PaaS)software as a service (SaaS)The term cloud is used as a metaphor for the Internet, based on how the Internet is depicted in computer network diagrams and is an abstraction for the complex infrastructure it conceals.
  • is held up as the classic example of SaaS – sign up and you have a full featured CRM available to you immediately. Configuration and customisation can all be done via your web browser. “Great – it fits in the SaaS box” you say…but not quite… is the platform under-pinning – and on you can build any type of application you like – CRM related or not. Often implementers will customise salesforce using the platform thereby creating, in effect a hybrid SaaS/PaaS offeringGoogle AppEngine and Windows Azure are essentially straight PaaS solutions – take your application component and deploy into the platform. Azure pushes into the IaaS aspects of cloud computing – for example, by offering relatively low level SQL Server features in a way not dissimilar to what you essentially get when starting an “off the shelf” Windows SQL Server AMI on Amazon EC2.Amazon EC2 is predominantly IaaS; and apart from some specific limitations, mainly around networking, is not too dissimilar from that of mass-market virtualisation providers or what large enterprise IT teams offer their internal customers in “private clouds”.
  • With AWS a new server can be up and running in three minutes (it used to take Eli Lilly seven and a half weeks to deploy a server internally) and a 64-node Linux cluster can be online in five minutes (compared with three months internally).
  • develop, test, deploy, host and maintain applicationssource code control, version control, dynamic (interactive) multiple user testing, roll out and roll back with the ability to audit and track who made what changes when to accomplish what purposeWeb based user interface creation toolsWYSIWYG etc etcMulti-tenant architectureIntegration with web services and databasesSupport for SOAP and REST interfaces allow PaaS offerings to create compositions of multiple Web services, sometimes called "Mashups".Support for development team collaborationThe ability to form and share code with ad-hoc or pre-defined or distributed teams greatly enhances the productivity of PaaS offerings. Schedules, objectives, teams, action items, owners of different areas of responsibilities, roles (designers, developers, tester, QC) can be defined, updated and tracked based on access rights.Utility-grade instrumentation
  • Resources delivered as a service including servers, network equipment, memory, CPU, disk space, data center facilities,Dynamic scaling of infrastructure which scales up and down based on application resource needs AMAZON 50k per dayVariable cost service using fixed prices per resource componentMultiple tenants typically coexist on the same infrastructure resourcesEnterprise grade infrastructure allows mid-size companies to benefit from the aggregate compute resource pools
  • No huge capital investment required so less risky financiallyMinimises time to value period – 30 day free trial shows quick benefitsEncourages consistent utilisation and therefore reduces roll out headachesSaaS reduces IT depts requirements to spend time sysadmining – therefore can do higher value strategic IT stuff
  • - The data from the 3rd party is normally available via a web application which is human accessible only.- In order for anyone to see the data, they need to log in and then drill down to the level they require.- The layout of the web application is somewhat convoluted and not suitable for executive level.- The data is made suitable for display in executive summary by automating the data access via the 3rd party API
  • Need to assess how change will effect existing IT assetsAssess data security needs and ensure external SaaS provider can meet organisation’s requirementsGiven that SaaS has traditionally been seen as a SME delivery methodology – SaaS providers may not have service level agreements already in place – need to ensure SLAs are in place, guarantees are sufficient to meet organisational needs and mitigation provisions are sufficient to cope with a “worst case” situationEnsure prospective SaaS provider has data-migration functionalities in the event that later migration from the SaaS product is required. Ensure access to raw data and contractual agreed access to organisational dataObvious need to ensure that SaaS product will integrate with other organisationally used applicationsIn these post enron days and with sarbanes-oxley requirements SAS70 (Statement on auditing standards #70) is a major issue. Need to ensure SaaS provider can provide a SAS70 report and that it meets organisational requirements in terms of privacy and data securityIT departments embracing an open outsourcing or SaaS perspective need to see themselves not as IT gatekeepers but internal consultants offering advice, deployment services and mission critical IT functionality. It moves IT from a technology-centric approach to a service-centric one where it can add value to the organisation within which it operates
  • Cloud Computing 101

    1. 1. An Overview of Applications that are Currently Delivered via the Cloud and Potential Applications for the Future<br />Ben Kepes<br />Diversity Limited <br />NZ Cloud Computing Summit<br />October 2009<br />Photo credit - svanes<br />
    2. 2. Agenda<br />Who am I?<br />Understanding Cloud Computing<br />Understanding SaaS<br />Understanding PaaS<br />Understanding IaaS<br />Cloudy Effects<br /> Looking to the future<br />
    3. 3. Ben Kepes<br /> Editor - CloudAve<br /> Cloud computing commentator<br />Advisor<br /> Evangelist<br />
    4. 4. Understanding Cloud Computing<br />Is it…<br />Software as a Service?<br />Cloud Storage?<br /> Platform as a Service?<br /> Virtualisation?<br />Infrastructure as a Service? <br /> Multi Tenancy?<br />Web 2.0?<br />Outsourcing? <br />
    5. 5. YES!<br />
    6. 6. So What is Cloud Computing?<br />
    7. 7. What is Cloud Computing Really?<br />
    8. 8. Understanding Cloud Computing<br />Scalability<br />Instantaneousness<br />Pay according to use<br /> Focus on core business<br />Reliable/Stable/Ease of use<br />
    9. 9. Cloud Computing in a few more minutes<br />
    10. 10. Understanding Cloud Computing<br /> Cloud can be a utility model – a software model of electricity, water or telco delivery<br />Users need not have expertise over technology infrastructure<br />It can be a way to gain infrastructural efficiencies<br /> An easy development platform<br />
    11. 11. Understanding Cloud Computing<br />Source – Fronde Blog<br />
    12. 12. “ …everyone on the planet deserves to have their own virtual data center in the cloud ”<br /> - Lew Tucker, CTO of SUN cloud group<br />
    13. 13. “ …we are able to reduce our IT operational costs by roughly 30% of what we’re spending now ”<br />- Ingo Elfering, Vice President of Information Technology Strategy, GlaxoSmithKline<br />
    14. 14. “ The deployment time is really what impressed us, it&apos;s just shy of instantaneous ” <br />- Dave Powers Associate Information Consultant, Eli Lilly<br />
    15. 15. Understanding SaaS<br />Modern version of application service providers (ASPs) but,<br />Custom created for web based delivery<br /> Single instance, multi-tenant architecture<br /> Provider patch and upgrade management<br />May include application programming interfaces (APIs)<br />Generally subscription basis – per seat, user, instance<br />
    16. 16. Cloud Deployment Case Study #1<br />A cloud based billing system powers online delivery of micro format news <br />
    17. 17. Saving Traditional Media<br />Reed Business Information - 400 publications - 200 online properties<br /> Needed comprehensive billing functionality<br />Needed simple integration with SFDC, Oracle, Website <br /> Needed simple implementation<br /> Needed affordability and minimal CAPEX<br />
    18. 18. Saving Traditional Media<br /> Media content located within traditional media dataspace<br /> utilise advanced tagging to categorise content<br /> subscribe via a SaaSbilling platform<br />Receive the content you want, how you want it <br />
    19. 19. Understanding PaaS<br />Services to develop, test, deploy, host<br />Web based user interface<br />Multi-tenant architecture<br />Integration with web services and databases<br />Support for development team collaboration<br />Utility-grade instrumentation<br />
    20. 20. Cloud Deployment Case Study #2<br />Quoting system created on PaaS, integrated with SaaS CRM and SaaS Accounting <br />
    21. 21. Driving Efficiencies<br />CyberSafesecurity solution provider<br />Utilisedon-premises contact manager/accounting<br /> Needed quoting system <br /> Wanted integration with contact manager<br /> Wished to retire disconnected legacy system<br />
    22. 22. Driving Efficiencies<br /> Implemented SaaS CRM in 2002<br /> utilised PaaS to develop custom-built quoting system<br />integrated automatically via PaaS with<br />Deployed Coda2go SaaS accounting application<br /> leveraging totally connected cloud based SaaS/PaaS<br />
    23. 23. “Services designed to scale to tens or hundreds or millions of users will dramatically change the nature and cost of solutions deliverable to enterprise..”<br /> - Bill Gates<br /> Microsoft Internal memo<br />
    24. 24. “I believe, over time, more and more software will be delivered as a service. I totally believe that... We have to be good at this, or we have a problem”<br /> - Larry Ellison CEO Oracle<br />
    25. 25. Understanding IaaS<br />Resources delivered as a service <br /> Dynamic scaling of infrastructure<br /> Variable cost service<br /> Multiple tenants on the same infrastructure resources<br />Enterprise grade infrastructure<br />
    26. 26. So... About Cloud being just for SMBs<br />Manages risks of acquisition of software<br /> Minimises roll-out requirements<br />Keeps IT strategically focussed<br />Eases pain of managing on-premise apps<br />
    27. 27. Cloud Deployment Case Study #3<br />Utilising data and graphical processing services from the cloud for an inside-the-firewall analysis… <br />
    28. 28. Enterprise Data Visibility<br />human readable 3rd party website that is too technical and complex for exec level readership<br /> utilise 3rd party API to get only the data needed for exec summary<br /> summarize this in enterprise dashboard for exec level readership<br />utilize charting to represent trends over time <br />
    29. 29. SaaS Deployment Case Study<br />
    30. 30. How will the cloud affect the organisation?<br />IT governance implications<br />Security needs<br />Service level agreements (SLAs)<br />Migration strategies<br /> In-house integration<br />Regulatory impacts<br />IT Role impacts<br />
    31. 31. Balancing the financial implications<br />
    32. 32. Cloud Deployment Case Study #4<br />Start up company – on premise IT free zone<br />
    33. 33. IT Free Zone<br />Company experienced rapid growth (400% employee count growth in one month)<br /> Philosophy: “IT Free Zone”<br />Only IT around the office: Laptops, WiFi, Printer<br />
    34. 34. IT Free Zone<br />IaaS – GoGrid, Media Temple, Amazon EC2<br />PaaS -<br />SaaS – Salesforce, Xero, Google Apps<br />
    35. 35. Advantages?<br />Quick office set up, just a few hours<br />Radically reduced cost of IT, setup and ongoing<br /> Minimal Capex<br />Staff access/collaboration<br />Remote work, from office to home<br />
    36. 36. And to the Future?<br />No more in-house infrastructure<br />Ubiquitous access from situational devices<br />Ability to rapidly develop, test and deploy even extreme edge solutions<br />Upswing in business unit innovation<br />Better, Stronger, Faster<br />
    37. 37. Next steps…..<br />Try it out – Cloud isn’t completely terrifying<br />Spin up a server on Amazon<br /> Store something on S3 or an end-user service<br />Try out a consumer SaaS application<br /><br />