Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cloud Presentation Cloudbook Gia Slideshare


Published on

The presentation I held on 14 jan 2010 for 'Genootschap Informatie Architecten' about cloud computing. It is an addon to the cloudcomputing book published by TIEM.

Published in: Technology, Business
  • Be the first to comment

Cloud Presentation Cloudbook Gia Slideshare

  1. 1. Subjects:<br /><ul><li>Introduction
  2. 2. Cloud Integration
  3. 3. Future</li></ul>On to the<br />Introduction<br />
  4. 4. Cloud computing is a pay-per-use model for enabling available, convenient, on-demand accessto a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction. <br />Lots of definitions of Cloud Computing<br />
  5. 5. Definitions of Cloud Computing<br />Clouds are hardware-based services<br />offering compute, network and storage capacity where: <br />▪ Hardware management is highly abstracted from the buyer<br />▪ Buyers incur infrastructure costs as variable OPEX<br />▪ Infrastructure capacity is highly elastic (up or down)<br />
  6. 6. Quotes<br />“Cloud computing has the potential to create irreversible changes in how computers are used around the world”<br />“Cloud computing technology’s objective is to move any application stored on a computer to a remote location, eliminating all the standard components, including operating systems and hard drives, which are necessary in today’s computers and make them accessible online through a standard browser. “<br />
  7. 7. Simple Cloud Definition<br />Resources As A <br />Commodity<br />Comparable to a supermarket<br />
  8. 8. How IT used to be.<br />That’s 3 servers, 15 licences, 4 routers, 2 networks…. <br />Do you have an online webshop for me?<br />Switching over from request<br />to demand based……….<br />
  9. 9. Infrastructure<br />AS A SERVICE<br />Platform<br />Software<br />Deployment Models<br />
  10. 10. Setup your own cloud-service<br />Datacenter on SOAP<br />Basic costs: <br />Connectivity<br />CPU<br />Storage<br />Direct and On-Demand Provisioning<br />Differentiated by smart network services<br />Infrastructure As A Service<br />
  11. 11. Specific platform that is programmable.<br />Infrastructure transparent<br />On demand up and down scaling<br />Provide a technology lock-in<br />Reseller models for applications<br />Samples: Google AppEngine,, ZOHO<br />Platform As A Service<br />
  12. 12. ASP application with cloud characteristics<br />Integration standards are missing<br />Possible lock-in<br />Fast growing segment with startups:<br />Photo/Video sites<br />Consumer Financials<br />Social<br />Software As A Service<br />
  13. 13. Factors<br />Connectivity<br />GRID<br />Cost reduction. Focus on operational expenses.<br />Flexibility. IT support should be up to web-speed.<br />High level SLA.<br />Usage based cost model.<br />Easy upscaling. <br />Less maintenance. Less visible technology.<br />Open standards.<br />Easy to control and maintain.<br />Costs<br />Online<br />Apps<br />Green IT<br />Privacy<br />Outsourcing<br />2.0<br />2.0<br />
  14. 14. Type Of Clouds<br />Public Clouds<br />Everything for the end-user<br />Private Clouds<br />Plain Old Data Center Infrastructure (mostly NOT!)<br />Off-premise Specialized Cloud<br />How your IT should work<br />Hybrid Clouds<br />Surge computing (on demand capacity)<br />
  15. 15. About the Economy Of Scale<br />Rules of the supermarket apply:<br /><ul><li>Just-In-Time planning
  16. 16. Demand based warehouse management
  17. 17. Operational excellence
  18. 18. A tiny optimization can already lead to profit
  19. 19. Expensive in CAPEX, low in OPEX</li></ul>Sample of Microsoft Datacenter Strategy :<br />
  20. 20. Global References <br />Amazon Web Services :<br />Microsoft <br />Azure : (iaas)<br />BPOS :<br /><br />platform<br />Application<br />Google<br />AppEngine (paas)<br />Apps (saas)<br />
  21. 21. Next:<br /><ul><li> Introduction
  22. 22. Cloud Integration
  23. 23. Future</li></ul>About<br />Cloud Integration…<br />
  24. 24. Cloud integration mechanisms<br />Decoupled<br />Store-front<br />Inside-Out<br />
  25. 25. About Seperation Of Concern<br />Business<br />Process<br />Online delivers online functionality based on:<br /><ul><li> Requests from the business
  26. 26. Available services</li></ul>If functionality is needed online that is not currently available through services this should be arranged directly. <br />Online<br />website<br />The separation of concerns between the process and business part of the organization should be reflected in the architecture.<br />
  27. 27. Build to change vs. Design to last<br /><ul><li>Build to change:
  28. 28. Agile development and deployment
  29. 29. Quick incorporation of new presentation standards
  30. 30. Design to last
  31. 31. Fixed interfaces, comprehensive definitions
  32. 32. Focused on the process
  33. 33. 40/30/20/10% rule applies</li></ul>Frontends<br />Services<br />
  34. 34. Decoupled:<br />1<br />SFA<br />HRM<br />KMS<br />Custom<br />Force<br />Sites<br /><br />Force<br />Sites<br />Force<br />Sites<br />2<br />3<br />SAP<br />SAP initiates import and export of data. Orders in are unresolved and new customers will be leads until a successful feedback of the backend is given.<br />This mechanism is called decoupled and requires not much changes on the current IT landscape.<br />Independent development of steps is possible:<br />Front-end User Interface (starting with leads)<br />Loading of customer data from your backend<br />Getting contracted updates and changes to your backend<br />
  35. 35. References Decoupled<br /> ( PAAS)<br /> (integration as a service)<br />
  36. 36. Decoupled<br /><ul><li>Can be implemented without backend where updates are managed manually
  37. 37. Strong separation of concern
  38. 38. Only keep parts highly available for the Internet and not for internal use (no costs)
  39. 39. No problems in maintenance and update schedules
  40. 40. Mandates an asynchronous application design.</li></li></ul><li>Storefront using AWS<br />Business<br />Build For Change<br />Process<br />Build To Last<br />CMS<br />HR<br />CRM<br />sales<br />DB<br />static<br />data<br />Process Layer<br />Online Integration (I/O)<br />CDN<br />BASIC<br />Customer<br />Data<br />Content<br />Data<br />Site<br />Logic<br />User (Browser)<br />
  41. 41. References Storefront<br />Amazon Cloudfront CDN :<br />Vordel XML Gateway appliance (for Online Integration layer):<br />
  42. 42. Storefront<br />Enhances the companies webpresence by placing this in the cloud<br />Physical separation of concern<br />Very fast and scalable for content<br />Technology independent because integration is in the frontend<br />
  43. 43. Example Inside-Out: Google<br /><ul><li> Extends current application infrastructure
  44. 44. Keeps secure data out of the cloud
  45. 45. High performance infrastructure needed which can be placed in a (private) cloud
  46. 46. Extends existing service oriented mechanisms</li></ul>Can also be used in other scenario’s as extension for the internal infrastructure.<br />
  47. 47. References Inside Out<br />Eucalyptus open elastic<br />Cast Iron integration appliance<br />
  48. 48. Inside Out<br />Use cloud resources when needed from inside:<br />Cloudbursting (hadoop)<br />Surge computing (cpu on demand)<br />Enterprise Application Webservices<br />For (more) mature IT environments<br />Scaling up performance, scale back IT<br />
  49. 49. What to use?<br />Inbound<br />logistics<br />Opera<br />tions<br />Outbound<br />Logistics<br />Marketing<br />& Sales<br />Service<br />Inside-Out<br />Decoupled<br />Store-front<br />Sample of an basic architecture based on Porter’s Value Chain<br />
  50. 50. Migration Tactics<br /><ul><li>Slow adoption strategyUse a small feature basis and roll-out new ones weekly instead of big bang
  51. 51. Use intermediate data formatsMigration data always in independent formats for rollback/alternative scenario
  52. 52. Plan company data backup (retention)
  53. 53. Network and infrastructure planningSince network connectivity is key for cloud</li></ul>Fail fast,<br />Fail Often<br />Release Early<br />Release Often<br />
  54. 54. Next:<br /><ul><li> Introduction
  55. 55. Cloud Integration
  56. 56. Future</li></li></ul><li>Future<br />Personal Enterprise Services<br />Open Networks Everywhere<br />Generation Y / Responsibility<br />Bring Your Own Hardware and Get Your Own Services<br />Internet/Cloud of Things<br />