Infrastructure

A practical guide to platform as a service: PaaS benefits and characteristics

Share this post:

PaaS-Benefits-500x357One of the major benefits of platform as a service PaaS is its ability to improve a developer’s productivity. PaaS provides direct support for business agility by enabling rapid development with faster and more frequent delivery of functionality. It does this through continuous integration techniques and automatic application deployment. PaaS also enables developers to realize the cloud’s broader benefits.

This includes:

  • Scalability, including rapid allocation and deallocation of resources with a pay-as-you-use model (noting that the use of individual resources can vary greatly over the life cycle of an application)
  • Reduced capital expenditure
  • Reduced lead times with on-demand availability of resources
  • Self-service with reduced administration costs
  • Reduced skill requirements
  • Support of team collaboration
  • Ability to add new users quickly

The automation support one receives in a PaaS environment also provides productivity improvements and consistency in delivery. Along with automation is the ability for closer equivalence of the development, test and production environments, again improving consistency and reliability of delivery. This is one aspect of a DevOps/agile development approach that is ideal for a PaaS environment.

[Related post: A practical guide to platform as a service: What is PaaS?]

In addition, PaaS systems typically enable the sharing of resources across multiple development teams, avoiding the need for wasteful allocation of multiple assets of the same type in separate silos.

PaaS systems typically build in security and data-protection features, including resilience capabilities such as replication and backups. This can improve security and reduce the need for in-house security skills.

The provision of sophisticated, off-the-shelf capabilities as services enables the rapid creation and evolution of applications that address business requirements. This is especially important when considering mobile and web applications that include social and Internet of Things (IoT) capabilities.

Business applications typically require integration and involve aggregation of data and services from multiple existing systems. PaaS systems usually feature prebuilt integration and aggregation components to speed and simplify necessary development work.

PaaS systems can be used to build applications that are then offered to other customers and users as a software as a service (SaaS) offering. The requirements of SaaS applications, including scalability and the ability to handle multiple tenants, can usually be met by the cloud computing capabilities of a PaaS system.

In our next installment, we’ll provide guidance for acquiring and using PaaS offerings.

Interested in learning more about PaaS and getting a better picture of its implementation best practices? Check out my post on PaaS basics and download the Cloud Standards Customer Council’s “Practical Guide to Platform as a Service.”

More Infrastructure Stories

In the news: IBM Cloud Private

This month, IBM launched IBM Cloud Private, a scalable cloud platform built on open source frameworks and that runs on users’ own infrastructure. IBM Fellow Bala Rajaraman described it as a way to “use your heritage to your advantage.” But he’s not the only one talking about what IBM Cloud Private can do. Numerous print […]

Continue reading

Why managed services are key to driving cloud results

Many cloud hosting vendors have invested heavily in large-scale distributed data centers for cloud infrastructure as part of their business model. Over the last few years, the cloud model has become very efficient, being self-driven through websites for cloud provisioning. A lot of features and functionality are added regularly. Numerous companies offer infrastructure as a […]

Continue reading

What’s stopping your cloud adoption?

As an IBM Cloud Adoption Leader, I spend a lot of time with clients who are implementing projects in the IBM Cloud. Typically, but not always, I get involved when there’s something blocking the project or otherwise hindering progress. These tend to fall into a small number of common categories: 1. The tools are not […]

Continue reading