PaaS, Present & Future: Developers Will Decide - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Cloud // Platform as a Service
Commentary
3/20/2014
11:35 AM
Ric Telford
Ric Telford
Commentary
Connect Directly
Twitter
RSS
E-Mail
100%
0%

PaaS, Present & Future: Developers Will Decide

Platform-as-a-service differs from IaaS. IBM's Ric Telford predicts what we'll see as it matures during the next two years.

More than two years ago I wrote the blog post "PaaS Comes Of Age," where I posited we were entering a platform-as-a-service era -- one in which platform services would become the critical cloud capability for enterprises. A lot has happened since I wrote that post, and now we are seeing this "coming of age" story continue into maturity.

For the uninitiated, PaaS can be thought of as a delivery model for functionality you traditionally associate with middleware. Not so coincidently, it also sits in the "middle" of the cloud stack, between infrastructure-as-a-service and software-as-a-service. PaaS can deliver any combination of application "development" and "runtime" services from the cloud, in some type of measured model (subscription, pay-as-you-go, etc).

Today there are quite a variety of PaaS services, so many that it's hard to keep them straight. Many companies have converged on this space, coming up from the IaaS layer (Amazon's Relational Database Service or Elastic Beanstalk), down from the SaaS layer (Salesforce's Force.com), or even as a new corporate initiative (Google AppEngine or Microsoft Azure). In addition, there are numerous "pure play" PaaS offerings (like EngineYard) and a whole slew of startups.

One aspect to watch carefully in the PaaS space is the role of open standards and open source. Unlike IaaS, where Amazon has become a bit of a de facto standard, PaaS is likely to be more de jure -- built on a set of open standards. IBM just announced BlueMix and a $1 billion commitment to PaaS capabilities. Key to this announcement was the support of Cloud Foundry, an open-source platform layer for the cloud. Started by VMware and spun off as part of Pivotal, Cloud Foundry already has around 40 corporate contributors. Not to be outdone, RedHat's OpenShift initiative is also based on open source and also has a stable of active contributors.

[Want more on Pivotal's latest moves? Read Pivotal Brings In-Memory Analysis To Hadoop.]

It will be interesting to see what the future holds for PaaS. If it tracks with similar technology shifts in IT history, here are some things to assume.

  • Companies need to become comfortable with the concept before they standardize on a PaaS. We are still in the tire-kicking stage in most enterprises, which want to see the value in PaaS before starting any serious shift off traditional middleware. This would imply a year or two before real PaaS growth. But, much like the shift from client/server applications to Internet-based applications, when the shift starts it will ramp quickly.
  • Open systems will coexist with proprietary. Much like Java and .Net, there will be followers of each.
  • Developers will decide. Think early days of Microsoft or today's Android. The PaaS vendors that are most successful in courting and keeping software developers will rise to the top. Don't be surprised if you start seeing some "PaaS-justifying applications" -- compelling SaaS offerings that run only on a particular vendor's PaaS. (For the gamers out there, an analogy is Titanfall for Xbox One.)
  • Consolidation will occur, but not as much in the PaaS market as in IaaS. Some believe that IaaS vendors could consolidate down to as few as six major ones.
  • If you look at today's analogue -- the server and storage business -- this seems about right. But PaaS is a much broader set of capabilities, and one in which ecosystems can develop around standards (much like the Java community today), but still have room for a larger field of competitors.

I will check back in two more years and see if these predictions prove to be accurate.

Please post your comments below. You can also follow me on Twitter @rictelford as I track a lot of the happenings in the world of cloud, or look me up on LinkedIn.

Private clouds are moving rapidly from concept to production. But some fears about expertise and integration still linger. Also in the Private Clouds Step Up issue of InformationWeek: The public cloud and the steam engine have more in common than you might think. (Free registration required.)

Ric Telford is VP of IT Services Strategy and Cloud at IBM. His career highlights 30 years of software development, IT service delivery and business strategy.  Ric has not only developed systems but also delivered them.  He has been involved with cloud for the last ... View Full Bio

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Charlie Babcock
100%
0%
Charlie Babcock,
User Rank: Author
3/24/2014 | 3:59:37 PM
PaaS resembles language frameworks on steroids
These comments on PaaS remind me of how programmer's frameworks first emerged for particular languages, such as Spring and Ruby on Rails.The cloud offers a multi-language setting where the same plumbing, middleware and aids to application development can be readily assembled. The potential is much greater in the cloud because its a future deployment environment after dev., as well.
Charlie Babcock
100%
0%
Charlie Babcock,
User Rank: Author
3/20/2014 | 12:51:16 PM
PaaS will tend to be open source and come in flavors
An excellent discussion of PaaS, Ric, and some telling points on how standards and open source code will have a lot to say about which types of PaaS survive and thrive. VMware/Pivotal had good foresight to build a successful open source project around Cloud Foundry. More power to them. Google App Engine and Microsoft Azure are different beasts where the PaaS closely resembles the infrastructure as a service itself, and applications that developers compose there should probably be run there. Red Hat OpenShift will bring additional standards and open source, with expertise in the Linux kernel and Linux Containers. It may develop its own distinctive flavor of PaaS.
InformationWeek Is Getting an Upgrade!

Find out more about our plans to improve the look, functionality, and performance of the InformationWeek site in the coming months.

News
Remote Work Tops SF, NYC for Most High-Paying Job Openings
Jessica Davis, Senior Editor, Enterprise Apps,  7/20/2021
Slideshows
Blockchain Gets Real Across Industries
Lisa Morgan, Freelance Writer,  7/22/2021
Commentary
Seeking a Competitive Edge vs. Chasing Savings in the Cloud
Joao-Pierre S. Ruth, Senior Writer,  7/19/2021
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Monitoring Critical Cloud Workloads Report
In this report, our experts will discuss how to advance your ability to monitor critical workloads as they move about the various cloud platforms in your company.
Slideshows
Flash Poll