inleiding tot cloud computing

Presentatie over: "inleiding tot cloud computing"— Transcript van de presentatie:

1 inleiding tot cloud computing
4 november 2014 Titel slide

2 agenda 1 inleiding 2 drivers & barriers 3 verschijningsvormen
4 advies aanpak 5 afsluiting

3 social business consultant
Emma Kastelein social business consultant Visitekaartje/ voorstellen presentator

4 Wat valt je op?

5 IaaS PaaS SaaS Toelichting Infrastructure/platform/software as a Service = I/P/SaaS. History repeats. Uitleg dat public utilities vergelijkbare ontwikkeling hebben doorgemaakt. Elektriciteit werd eerst door onsite generatoren opgewekt; daarna voor het publiek afneembaar as a service  IaaS Voorbeelden paas [Google App Engine, Windows Azure, Cloud Foundary, Force.com], saas [Google Gmail, Microsoft 365, Salesforce, Citrix GoToMeeting, Cisco WebEx].

6 On Premises Infrastructure Platform Software Storage Servers
Networking O/S Middleware Virtualization Data Applications Runtime You manage Infrastructure (as a Service) Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime Managed by Microsoft You manage Platform (as a Service) Managed by Microsoft You manage Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data Software (as a Service) Managed by Microsoft Storage Servers Networking O/S Middleware Virtualization Applications Runtime Data Slide Objectives: Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail. Speaking Points: Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure. Packaged Software With packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaS With Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering. Very few actually provide an OS The customer is still responsible for managing the OS through the Applications. For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines. This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2). Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’. The only requirement was a credit card to pay for the services. PaaS With Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor. The Windows Azure best fits in this category today. In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS. PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services. With PaaS, the developer can, almost immediately, begin creating the business logic for an application. Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly. SaaS Finally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.

7 history repeats… Toelichting Infrastructure/platform/software as a Service = I/P/SaaS. History repeats. Uitleg dat public utilities vergelijkbare ontwikkeling hebben doorgemaakt. Elektriciteit werd eerst door onsite generatoren opgewekt; daarna voor het publiek afneembaar as a service  IaaS Voorbeelden paas [Google App Engine, Windows Azure, Cloud Foundary, Force.com], saas [Google Gmail, Microsoft 365, Salesforce, Citrix GoToMeeting, Cisco WebEx].

8 agenda 1 inleiding 2 drivers & barriers 3 verschijningsvormen
4 advies aanpak 5 afsluiting

9 drivers 1 kostenreductie 2 verandering bedrijfsprocessen
3 nieuwe markten 4 interactie met klant

10 “It’s a transformative journey that will catalyze change across the organization. As such, it is critical that organizations dedicate sufficient budget over appropriate timelines to support the transformative change that will need to occur as cloud is rapidly adopted into the enterprise.” Egidio Zarrella, Cloud Leader, KPMG in China

11 barriers 1 implementatiekosten 2 integratie bestaande systemen
3 intellectueel eigendom 4 data- en privacyverlies 5 controle 6 regelgeving

12 agenda 1 inleiding 2 drivers & barriers 3 verschijningsvormen
4 advies aanpak 5 afsluiting

13 verschijningsvormen A continuum of cloud services public private
Verschijningsvormen plus enkele voorbeelden. hybrid A continuum of cloud services

14 agenda 1 inleiding 2 drivers & barriers 3 verschijningsvormen
4 advies aanpak 5 afsluiting

15 advies aanpak formuleer een visie integrale benadering
adaptief vermogen vertaal door vanuit bedrijfsdoelstellingen advies aanpak faseer en creëer vertrouwen business case …

16 T-score = M (otivatie) x C (apaciteit) x G (elegenheid)
Veranderend vermogen Triade model van Theo Poiesz T-score = M (otivatie) x C (apaciteit) x G (elegenheid)

17 Leestips Cloud Services for Dummies
The Cloud takes shape: the implementation challenge /cloud-service-providers-survey/Documents/the-cloud-takes- shapev2.pdf Gedragsmanagement, Prof.dr. Theo B.C. Poiesz, 1999

18 Bedankt voor jullie aandacht
Emma Kastelein social business consultant