Platform as a Service (PaaS)

Platform as a Service, often simply referred to as PaaS, is a category of cloud computing that provides a platform and environment to allow developers to build applications and services over the internet. PaaS services are hosted in the cloud and accessed by users simply via their web browser.

Platform as a Service (PaaS) delivers application execution services, such as application runtime, storage, and integration for applications written for a pre-specified development framework. PaaS provides an efficient and agile approach to operate scale-out applications in a predictable and cost-effective manner. Service levels and operational risks are shared because the consumer must take responsibility for the stability, architectural compliance, and overall operations of the application while the provider delivers the platform capability (including the infrastructure and operational functions) at a predictable service level and cost.

Platform as a Service allows users to create software applications using tools supplied by the provider. PaaS services can consist of preconfigured features that customers can subscribe to; they can choose to include the features that meet their requirements while discarding those that do not. Consequently, packages can vary from offering simple point-and-click frameworks where no client side hosting expertise is required to supplying the infrastructure options for advanced development.

The following diagram shows how PaaS offers an API and development tools to the developers and how it helps the end user to access business applications.

Platform as a Service

Benefits of PaaS cloud computing layer

1) Simplified Development

Developers can focus on development and innovation without worrying about the infrastructure.

2) Lower risk

No requirements of up-front investment in hardware and software. Developers only need a PC and an internet connection to start building applications.

3) Prebuilt business functionality

Some PaaS vendors also provide already defined business functionality so that users can avoid building everything from very scratch and hence can directly start the projects only.

4) Instant community

PaaS vendors frequently provides online communities where developer can get the ideas, share experiences and seek advice from others.

5) Scalability

Applications deployed can scale from one to thousands of users without any changes to the applications.

Disadvantages of PaaS Layer

1) Vendor lock-in

One have to write the applications according to the platform provided by PaaS vendor so migration of an application to another PaaS vendor would be a problem.

2) Data Privacy

Corporate data, whether it can be critical or not, will be private so if it is not located within the walls of the company there can be a risk in terms of privacy of data.

3) Integration with the rest of the systems applications

It may happen that some applications are local and some are in cloud. So there will be chances of increased complexity when we want to use data which in the cloud with the local data.

PaaS Types
Based on the functions, the PaaS can be classified into four types as shown in the following diagram:

Platform as a Service  (PaaS)

Top vendors who are providing PaaS cloud computing platform

  • Google Apps Engine (GAE)
  • SalesFroce.com
  • Windows Azure
  • AppFog
  • Openshift
  • Cloud Foundary from VMware

1. http://en.wikipedia.org/wiki/Platform_as_a_service

<<Previous <<   || Index ||   >>Next >>


  1. Thanks Dinesh for this wonderful tutorial , the same integration of Spring 3.0 can be acheived through Struts 1.x , if so then how to do that pls, show a simple registration ex. for practice purpose......

    pls reply asap
    rajeev singh

  2. Paritosh MaheshwariMay 22, 2014 at 7:56 AM

    Hi Dinesh, I want to point towards one very important aspect.
    Why you have not given the scope of the UserAction and UserBean in the spring configuration file? Are you sure these will be in singleton scope? To my knowledge, Struts2 will create a new instance of these on each user request.

  3. That is why we are using spring IOC.

  4. Paritosh MaheshwariMay 25, 2014 at 10:10 AM

    Ok, thanks for the reply. My precise question is why you are not defining the scope of the UserAction as "Prototype". As per "Struts 2" details, it will not create just once instance and use the thread for multiple user requests. It will create one instance for each request of the Action Class, since the action class is not the playing the same role as used to play in Struts 1.0.

  5. Thanks Dinesh. If I insert alphabetic character into UserAge. After pressing user button ,the invalid field value for field "userage" is show on the message . I change to number in text box of User age . The same message is
    shown on screen. Do you have any idea to solve the problem ? Thanks

  6. plz use trim() method I think you have space in value.