|Ph. D. Julio Fernandez Vilas|
|¿Any comments? [email protected]|
So far everything that relates to the architecture of Cloud-based technology model. With regard to the implementation model or working model, we distinguish at least 3 entities, although each of them may be subdivided depending on the business needs:
a) Infrastructure Provider is the entity that provides services in the cloud.
b) Service Provider is the entity that consumes the services to be offered to a third party.
c) Client Service is the final consumer.
This, with a real example would look something like:
According to the Gartner report on the current state of cloud technologies (http://www.gartner.com/document/2515316, access rights maybe required), today we can separate it into 4 modes according to "how" the customer manages the infrastructure used in the cloud:
a) IaaS+ Middleware. In this mode the client (subscriber) manages the infrastructure and is responsible for deploying their own middleware (or use pre-built middleware that facilitates the service provider models).
b) IaaS Cloud-Enabled. For the customer remains IaaS mode, but the provider handles the scaling part (elasticity platform).
c) PaaS Cloud-Based. This is where the great change in the way we manage. In client mode only PaaS handles the functionality of the platform, and is the provider who manages the hardware and software infrastructure.
d) PaaS Cloud-Native. The operation mode is the same as in the previous model, with the addition that the middleware layer is designed and configured to work in cloud mode.
In the figure below we can see the different "grade of management" that must perform the subscriber of different cloud services based on the hired mode.