The last thing we'll talk about in this module is the so called Cloud Services models.
The National Institute of Standards and Technologies outlines three different service models that are crucial for understanding the cloud.
Those three service models are compared to the traditional model for pricing software applications in your own data center, also called the on premises model.
If you have your own data center on premises, you are responsible for buying, setting up and managing the whole stack for your application.
This includes hardware like networking, storage and servers.
You also need to configure the virtualization, install the operating system on the servers and set up any middleware and run times that your application will need.
you need to deploy your application and manage the data it stores and uses.
The first Cloud Service model is called infrastructure as a service,
infrastructure as a service is very similar to the on premises model.
However, in the case of infrastructure as a service, the cloud vendor is responsible for managing the hardware in the virtualization layer, giving you complete control on the choice of operating system and the rest of the stack.
Of course, you pay some price for the services provided by the cloud vendor.
The benefit of this model is that you don't need to deal with setting up and managing the lowest level components of the stack.
And, more importantly, you don't need to spend tons of money initially to buy the hardware, Acquire a building and deal with utilities.
Platform as a service or
pause is the next level of instruction.
In this model, the vendor manages everything else except your application and data.
This is very useful for rapid development of applications because development teams don't need to spend time managing the infrastructure and the runtime components.
The last model is called software as a service.
In this case, the vendor manages everything and you just consume the software.