I am not criticizing the strategies behind

[sujonkumar6300]

This resounding term. On the contrary, they are very convenient when it comes to implementation, and as software development professionals we have the obligation to be familiar with them. What I am criticizing is the abuse of an ambiguous term, which often gets implementers into trouble because it is not clearly understood.

Most of the references I consulted mention three main layers or levels: Software –or application– as a service (Software as a Service, SaaS), Platform as a Service (Platform as a Service, PaaS) and Infrastructure or hardware as a service UK Mobile Database (Infrastructure as a Service, IaaS). My point of view is that, rather than a different level, IaaS is a set of additional qualities that give added value to a PaaS offering.

SaaS: Building Blocks

When one of our systems uses a remote public API, or when our workflow uses an application that resides and is managed outside of our organization, we are using SaaS. Our vendor may charge for their service in a variety of ways: through direct rent, by requiring advertising, by receiving permission to collect and data mine our information — There are a huge variety of schemes, reflecting the wide variety of levels of integration that can be given to the services.