Recommended
More Related Content
Similar to M1 Presentation Slides-copy.pptx
Similar to M1 Presentation Slides-copy.pptx (20)
Recently uploaded
Recently uploaded (20)
M1 Presentation Slides-copy.pptx
- 1. LO1a: Describe the three main service models (IaaS/PaaS/SaaS) of Cloud Computing. 1
- 3. Three Service Models ⬡ Infrastructure-as-a-Service (IaaS) ⬡ Platform-as-a-Service (PaaS) ⬡ Software-as-a-Service (SaaS) 3
- 4. Three Service Models ⬡ Infrastructure-as-a-Service (IaaS) ⬡ Platform-as-a-Service (PaaS) ⬡ Software-as-a-Service (SaaS) 4 Ref: https://docs.microsoft.com/en-us/learn/modules/fundamental-azure-concepts/categories-of-cloud-services
- 5. Shared Responsibility Model 5 Ref: https://digitalcloud.training/cloud-computing-service-models-iaas-paas-saas/
- 7. Ref: AWS Introduction and History - AWSome Day Online Conference - APAC Traditional vs Cloud IaaS
- 8. Cloud Data Centre 8 Virtualized Compute Virtualized Storage Virtualized Network Server Server Server Hypervisor Hypervisor Hypervisor Resource Pooling Compartments IaaS Customer 1 IaaS Customer 2 Hardware PaaS Customer 3 PaaS Customer 4
- 9. Ref: AWS Introduction and History - AWSome Day Online Conference - APAC Foundation Services Platform Services
- 11. IaaS 11 ⬡ Offers Compute, Network & Storage in manner that are like those in typical data centers ⬡ Used by System Administrators ⬡ Pay for what you allocate ⬡ Most Control – more things to manage ⬡ Patching/updating of OS and
- 13. Cloud Data Centre 13 Virtualized Compute Virtualized Storage Virtualized Network Server Server Server Hypervisor Hypervisor Hypervisor Resource Pooling Compartments IaaS Customer 1 IaaS Customer 2 Hardware PaaS Customer 3 PaaS Customer 4
- 14. Ref: AWS Introduction and History - AWSome Day Online Conference - APAC Foundation Services Platform Services
- 16. PaaS 16 ⬡ Offers middleware, application servers, database servers ⬡ Used by Software Developers ⬡ Pay for what you use ⬡ Less Control – less things to manage ⬡ Patching/updating of OS and middleware by Cloud Service Provider
- 18. SaaS 18 • Many of the software we used today are SaaS. • People just pay for them and use their function without concerning themselves of how it works. Google Drives/Sheets etc.
- 19. SaaS 19 ⬡ Offers “software” services / applications ⬡ Used by End-users ⬡ Pay-per-use/subscription ⬡ Fully managed by Service Provider
- 20. SaaS 20 ⬡ Offers “software” services / applications ⬡ Used by End-users ⬡ Pay-per-use/subscription ⬡ Fully managed by Service Provider ⬡ From an IT professional point-of-view, it is how to leverage IaaS/PaaS to provide SaaS
- 21. Thank You 21
Editor's Notes
- <make sure share audio for Zoom is enable> Alright, I'll be presenting on my LO1a, which is to: "Describe the main service models of Cloud Computing."" The learners for this course are establishment or mid career IT professionals. Individuals who do not already know each other. The introduction part of the course would have talk about virtualization and common challenges that was faced by the learners.
- <Pause for class to be ready> Shall we begin? <RESET TIMER>
- Let's start off with the three main service models for Cloud Computing, which are: Infrastructure-as-a-Service, or I-a-a-S, Platform-as-a-Service, or P-a-a-S or you'll hear people pronounce it as PaaS, and... Software-as-a-Service, S-a-a-S or <pronounce "SaaS">. So what are these service models? Let's watch a video to learn more about them:
- All right, let's look at the three service models in more details. At very base of Cloud Computing is the Infrastructure-as-a-Service model, which covers pretty much things you would expect in a traditional data centre - the IT infrastructure, or the Compute, Storage and Networks. Platform-as-a-Service or PaaS builds on top of IaaS and adds the Operating System and Middleware, such as Application Servers and Database Servers as part of its services. Finally, SaaS, which leverages on the PaaS or IaaS to offer software services as Products (or in this slide, Hosted Applications) to end-users.
- So how do we decide which services to use? Well, part of the answer is knowing who, brings what to the table. This is define by what we call the Shared Responsibility Model. In traditional IT infrastructure, that is, when everything is on-premise, everything is taken care of by the IT infrastructure team. This means, the hardware, the Operating System, you know, Linux or Windows, the Runtime, such as your application servers or databases, the data, and of course, the application, like, for example, the SAP or the System used by Finance. In the IaaS, PaaS and SaaS model, you'll see that more of these responsibility is taken off the IT team and handled by the Cloud Service Provider. We'll go through these service models one by one.
- Infrastructure-as-a-Service <Pause>
- The left of this slide shows the traditional infrastructure, so you have things such as your storage, your servers, your network and of course, security on top of everything. In Infrastructure-as-a-Service, what the cloud service provider provides is very similar to what you are used to in the traditional data centre - just that they are typically virtualized. So, you will see things such as Virtual Machines, which is what, Azure, the Cloud from Microsoft, calls them, Amazon Web Services, or AWS likes to calls them Elastic Cloud Compute, i.e., EC2, where as Google calls them as Compute Engines. For Network, instead of router and switches, you get the functional equivalent in the form of Virtual Networks (VNet) for Azure, Virtual Private Cloud (VPC) for Amazon and Google. Of course, the equivalent for firewalls are provide as Security Groups, Network ACL, etc. What is important is to recognize that they are the same thing, but by different name.
- This is an diagram of how a Cloud Data Centre would be implemented. You'll have the physical hardware, and on top of which will be the hypervisor, such as VMWare, Nutanix, OpenStack, which will present the hardware resources as virtualized storage, network and compute. That is, you can think of it as taking all the physical hardware and pool them together to form one giant storage, network or compute, that can be partition into many smaller pieces for individual customers. Each piece can be virtually isolate from each other, even though they might be sharing the same hardware. By multiple customers sharing the same hardware pool, you get the benefit of resource sharing and pooling. Because as we know, not everybody needs the same resource at the same time.
- This is the various services from AWS. AWS calls these Foundation Services, which offers a bit more than purely IaaS. I've circled those that are part of the IaaS offering based on our understanding from the Shared Responsiblity Model. You have things like EC2, Elastic Load Balancer, VPCs, S3, etc.
- For Azure, they are placed under Infrastructure Service in this diagram. So you get things such as the Virtual Machines, Storage, and various network services, such as your Virtual Networks, Load Balancers, etc.
- So to summarize IaaS: IaaS offers Compute, network and storage in manner that are like those in typical data centers. Their target audiences or users are System administrators. The charging model is by what resources are allocated, like for example, how much CPU, RAM and Storage. Whether the resources is fully utilized or not, you pay the amount based on what you said you needed. The advantage is that there are no long term commitments and it is easier than traditional IT infrastructure to add or remove resources when needed. Of the 3 models, this give you the most control, which also means most work - you have to take care of the OS, middleware or runtime, data and application. Since you're taking care of the OS and middleware, it also means you're responsible for patching or updating of the system.
- Platform-as-a-Service Alright, let's move on to Platform-as-a-Service or PaaS
- Let's revisit how the Cloud Data Centre might be setup to provide Platform-as-a-Service. Well, the key to all cloud services is basically resource sharing. Typically, this means that the services are run on-top of the virtualized Compute, Storage and Network. But for some, they might prefer to run it on a separate resource pool from their IaaS offering or even as on bare metal servers, depending on the application, for performance reasons. So instead of having the users, deploy their database or application servers individually, the cloud service provider deploys them and make it available for all its users to use. Typically, database servers are expensive, so the cloud service provider could host a database server and sell database instances to customers, or an application server could be deployed to run many applications on top of it, and customer pays based on what they use.
- This is offering from AWS. They have classified most of their Platform-as-a-Service offerings under their Platform Services, with some in the Foundation Services that I'll consider to be PaaS as well. There' a long list, so I wouldn't go them, but they make it easier for a Software Developer to build applications by providing components they might need.
- Likewise, for Azure, you'll find them under the Platform Services. There's quite a lot of offerings as well, ranging from Databases or Data Services to Developer Services, to make it easy for developers to adopt DevOps in their workflow.
- So to summarize PaaS: PaaS offers middleware, application servers, database servers, or what the diagram over here refers to as "runtime" for the application. It's typically used by Software Developers, because they wouldn't need to take care of the lower level details such as installing and setting up the Operating System, Middleware, etc., but just deploy their code into the platform and run. Unlike IaaS, PaaS usually charges based on actual consumption, like how much actual CPU time is used. Since the Operating System, Middleware is taken care of by the Cloud Service Provider, and also, to allow things to run properly, the Cloud Service Provider has to standardize across many users, there is less control available to the user. The good part of it is that, it also means you don't have to manage the patching or updating of the Operating System and Middleware.
- Software-as-a-Service <Pause>
- Easy way to identify Software-as-a-Service - Unlike IaaS or PaaS, they are offerings for end-users, like consumers, finance, teachers and home-makers. In fact, the zoom session that we're using today is a SaaS offering. You pay a subscription to use Zoom, and you just use it without caring about how many servers or how much bandwidth is needed, to allow you to stream yourself to your audience. Or GMail or Google Sheets, you'll just go to gmail.com or sheets.google.com and not worry about what's going on behind the scene. So for SaaS, you'll typically just use the software or hosted applications without caring about how the underlaying IT is supporting it.
- Summary for SaaS: Saas offers "software" or services to end-users, that is, not necessary IT professionals. Typically, users pay a pay-per-use fee or subscription for these services. And, they are fully managed by the Service Provider, not necessary the Cloud Service Provider like Amazon, but the company offering the service, like Zoom, who in turn will liaise with the Cloud Service Provider such as Amazon, Azure or Google to make sure that their services run without interruption. You might notice that I didn’t show the service offerings from AWS or Azure for SaaS but jumped straight to the summary. Why is that so? Anyone? <Pause> <Next Slide for Answer>
- The reason I didn’t show the offering from the Cloud Service Providers is because typically, SaaS is offered not by the Cloud Service Providers but by Application Providers. As an IT professional, your company might want to offer its product as SaaS, and your task will most likely be to look at how to leverage on the scalability of IaaS or PaaS to make that happen.
- Alright, that's the end of the Three Service Models. Thank you! Can I get each of you to name one of the service model.