Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Learning from the PaaS

Jim Bugwadia | March 9, 2016
Container services are redefining PaaS by giving enterprises the freedom to choose best-of-breed tools and services to compose their own platforms

This vendor-written piece has been edited by Executive Networks Media to eliminate product promotion, but readers should note it will likely favour the submitter's approach.

Enterprises can now compose their own application platforms by selecting best of breed services for each layer. The portability and flexibility enabled by allowing users to control their application containers, also makes it easier for enterprises to leverage multiple cloud providers.

With the container services approach, there are no limitations or restrictions on development languages, tools, and services. Enterprises can now use open tools to package their application code into portable container images which are executed by the container services layer. This is essential for enabling Microservices style application architectures which are conducive to empowering small autonomous devops teams.

Application devops teams can choose their own shared services and standardize where it makes sense. The shared services may be run on the same container service, or in some cases may be entirely consumed as SaaS. A decision to change a language, or service for an application, does not impact the overall platform or other applications on that platform.

IT administrators now have full visibility and control of infrastructure services. The container services layer can help automate provisioning of infrastructure resources by integrating with infrastructure services, and without adding additional abstractions on the infrastructure layer. This allows enterprises to choose any cloud provider and leverage best practices for security and infrastructure management.

Container services are a game changer for application platforms. They enable all the benefits of a traditional PaaS, but without any compromises. Enterprise teams can now choose one or more cloud providers, select a container technology, select best-in-class container services and shared services, to compose their own platforms.

In my experience with customers at Nirmata (I am a co-founder), containerizing existing applications and adopting a container services approach and has led to significant improved efficiencies and developer productivity gains -- which translates to immediate cost savings and increased innovation for the businesses. It's a great time to be coding!

In 2009, the U.S. National Institute of Standards and Technology (NIST) published a draft definition of cloud computing. The NIST definition, created for government agencies buying cloud services, simplified cloud computing into three types of services: 1) IaaS (Infrastructure as a Service), where vendors offer on-demand compute, network, and storage; 2) PaaS (Platform as a Service), where vendors provide application development frameworks and deployment tools; and 3) SaaS (Software as a Service) where vendors deliver entire applications.

While IaaS and SaaS are well understood and widely adopted, PaaS has lagged behind. But I expect a massive surge in platform adoption in the next few years.

Why PaaS adoption has lagged


1  2  3  Next Page 

Sign up for MIS Asia eNewsletters.