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.

2. Cloud Integration

3. FutureOn to the Introduction

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. Lots of definitions of Cloud Computing

5. Definitions of Cloud Computing Clouds are hardware-based services offering compute, network and storage capacity where: ▪ Hardware management is highly abstracted from the buyer ▪ Buyers incur infrastructure costs as variable OPEX ▪ Infrastructure capacity is highly elastic (up or down)

6. Quotes “Cloud computing has the potential to create irreversible changes in how computers are used around the world” “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. “

7. Simple Cloud Definition Resources As A Commodity Comparable to a supermarket

8. How IT used to be. That’s 3 servers, 15 licences, 4 routers, 2 networks…. Do you have an online webshop for me? Switching over from request to demand based……….

9. Infrastructure AS A SERVICE Platform Software Deployment Models

10. Setup your own cloud-service Datacenter on SOAP Basic costs: Connectivity CPU Storage Direct and On-Demand Provisioning Differentiated by smart network services Infrastructure As A Service

11. Specific platform that is programmable. Infrastructure transparent On demand up and down scaling Provide a technology lock-in Reseller models for applications Samples: Google AppEngine, Salesforce.com, ZOHO Platform As A Service

12. ASP application with cloud characteristics Integration standards are missing Possible lock-in Fast growing segment with startups: Photo/Video sites Consumer Financials Social Software As A Service

13. Factors Connectivity GRID Cost reduction. Focus on operational expenses. Flexibility. IT support should be up to web-speed. High level SLA. Usage based cost model. Easy upscaling. Less maintenance. Less visible technology. Open standards. Easy to control and maintain. Costs Online Apps Green IT Privacy Outsourcing 2.0 2.0

14. Type Of Clouds Public Clouds Everything for the end-user Private Clouds Plain Old Data Center Infrastructure (mostly NOT!) Off-premise Specialized Cloud How your IT should work Hybrid Clouds Surge computing (on demand capacity)

16. Demand based warehouse management

17. Operational excellence

18. A tiny optimization can already lead to profit

19. Expensive in CAPEX, low in OPEXSample of Microsoft Datacenter Strategy : http://bit.ly/5X6sjn

20. Global References Amazon Web Services : http://aws.amazon.com Microsoft Azure : http://www.windowsazure.com (iaas) BPOS : http://www.microsoft.com/online/ Salesforce.com platform http://www.force.com Application http://www.salesforce.com Google AppEnginehttp://code.google.com/appengine/ (paas) Apps http://www.google.com/a (saas)

22. Cloud Integration

23. FutureAbout Cloud Integration…

24. Cloud integration mechanisms Decoupled Store-front Inside-Out

26. Available servicesIf functionality is needed online that is not currently available through services this should be arranged directly. Online website The separation of concerns between the process and business part of the organization should be reflected in the architecture.

28. Agile development and deployment

29. Quick incorporation of new presentation standards

30. Design to last

31. Fixed interfaces, comprehensive definitions

32. Focused on the process

33. 40/30/20/10% rule appliesFrontends Services

34. Decoupled: Force.com 1 SFA HRM KMS Custom Force Sites Force.com Force Sites Force Sites 2 3 SAP SAP initiates import and export of data. Orders in force.com are unresolved and new customers will be leads until a successful feedback of the backend is given. This mechanism is called decoupled and requires not much changes on the current IT landscape. Independent development of steps is possible: Front-end User Interface (starting with leads) Loading of customer data from your backend Getting contracted updates and changes to your backend

35. References Decoupled www.force.com (salesforce.com PAAS) http://www.informaticaondemand.com/ (integration as a service)

37. Strong separation of concern

38. Only keep parts highly available for the Internet and not for internal use (no costs)

39. No problems in maintenance and update schedules

41. References Storefront Amazon Cloudfront CDN : http://aws.amazon.com/cloudfront Vordel XML Gateway appliance (for Online Integration layer): http://www.vordel.com/products/vx_gateway/

42. Storefront Enhances the companies webpresence by placing this in the cloud Physical separation of concern Very fast and scalable for content Technology independent because integration is in the frontend

44. Keeps secure data out of the cloud

45. High performance infrastructure needed which can be placed in a (private) cloud

46. Extends existing service oriented mechanismsCan also be used in other scenario’s as extension for the internal infrastructure.

47. References Inside Out Eucalyptus open elastic http://open.eucalyptus.com/ Cast Iron integration appliance http://www.castiron.com/

48. Inside Out Use cloud resources when needed from inside: Cloudbursting (hadoop) Surge computing (cpu on demand) Enterprise Application Webservices For (more) mature IT environments Scaling up performance, scale back IT

49. What to use? Inbound logistics Opera tions Outbound Logistics Marketing & Sales Service Inside-Out Decoupled Store-front Sample of an basic architecture based on Porter’s Value Chain

51. Use intermediate data formatsMigration data always in independent formats for rollback/alternative scenario

52. Plan company data backup (retention)

53. Network and infrastructure planningSince network connectivity is key for cloudFail fast, Fail Often Release Early Release Often

55. Cloud Integration