Iaas and PaaS platform distinctions will soon become irrelevant, as OpenStack’s Solum project shows.
There’s been a renewed debate recently over the numerous layers of cloud computing stacks. At stake is a fight for cloud computing market share and mind share — and probably, the way forward for cloud platforms.
Beyond a small group of technologists, cloud computing remains largely a mystery for many people. Ironically, i suspect that is the point of the cloud: To behave as an abstraction of the complexity present in more traditional data centers and alertness hosting infrastructures.
At the guts of the cloud platform debate is a brand new reality: Cloud consumers not ought to manage or worry in regards to the underlying infrastructure. The question of platform occurs only for those who ask who or what controls operating systems, storage, deployed applications, and networking components. Platform as a service (PaaS) focuses not at the infrastructure pieces, but at the deployment of applications and configuration settings for the appliance-hosting environment. For many PaaS offerings, the preponderance of infrastructure features have been removed, and the focal point is on deploying a composable set of application components in preference to controlling the lower-level components.
[Concerns over NSA snooping are driving some companies clear of US-based cloud services. Read Foreign Businesses Flee US Cloud Computing, Survey Finds.]
But why does the consideration between IaaS and PaaS matter? Infrastructure as a service (IaaS) provides numerous features and benefits with regards to manipulating particular infrastructure components, although most remain unused. In PaaS, the vast majority of these infrastructure components had been removed, reducing complexity through improved automation, testing, and iteration of application components without the opportunity of introducing infrastructure-level bugs.
PaaS pundits will point to virtualization — or the dearth thereof — as a key differentiator, with technology like Linux containers offering improved deployment speeds. But this looks as if a red herring. Most IaaS platforms now support many varieties of virtualization. Startups like JumpCloud are bypassing the necessity for virtualization, instead settling on bare-metal hardware deployment. Recent improvements in traditional hypervisors have also reduced application deployment time to seconds, making the question of virtualization and its performance overhead practically meaningless.
The question is: Why are we, as an industry, spending lots time targeting building two distinct environments for cloud deployments? Do consumers really care concerning the difference between IaaS and PaaS?
Gordon Haff, a cloud evangelist at Red Hat, points out many of the challenges in a up to date blog post.
For most computing resource users, simply considering PaaS as the next level of abstraction than IaaS misses a big distinction. PaaS presents an abstraction that’s primarily utilized by — and of interest to — application developers. IaaS could also entice developers seeking more options and control. But a PaaS like OpenShift gives developers the tools they wish after which gets out of how. IaaS is infrastructure, and is therefore more excited by system admins who support developers (whether through a PaaS or otherwise) and other consumers of economic services. This may occasionally increasingly be the case, Haff says, as IaaS — or something adore it — develops into the traditional way computing infrastructures are built, whether at a cloud provider or in an enterprise.
Others see the convergence of infrastructure and platform layers as inevitable. One example is the Solum project, that is natively designed for OpenStack clouds. Per the project’s creators, Solum specializes in the intersection of the many parts of the cloud computing stacks, with a specific think about vendor neutrality, open design, and collaboration. It utilizes existing solutions where possible, for instance in its use of Docker for deployment of containers. Multiple language run-time environments could be supported with a modular language-pack solution so users can easily run applications written inside the language in their choice. Although projects like Solum are only getting started, they are able to point to a converged future, with both IaaS and PaaS in cloud computing stacks.
I also believe that traditional approaches to IaaS are too complex. From installation to deployment, to the continued management of cloud applications, the method has to be simplified. However, i am not convinced that using two distinct cloud computing environments is the reply. The lines between infrastructure and alertness have already blurred. As cloud systems become ubiquitous, classifying unique IaaS and PaaS layers turns into irrelevant.
At the top of the day, the simplest thing that actually matters in cloud computing is the API. APIs form a roadmap to the weather which are most crucial to cloud service consumers. The question becomes whether you select to exploit a selected API element. But even supposing you decide to not, it’s nice to understand that includes may well be potentially activated at a later date.
Some people say less is more. But on the planet of cloud computing, I say more is more (kind of).
Reuven Cohen was the founding father of Enomaly and creator of 1 of the primary IaaS platforms in 2005. He’s currently chief technology advocate at Citrix. (The views expressed don’t necessarily represent those of the author’s employer, Citrix Systems.)
Find Reuven on Twitter @rUv|Linkedin|Google+|Facebook|Podcast
Cloud Connect Summit, March 31 – April 1 2014, offers a two-day program colocated at Interop Las Vegas developed around “10 critical cloud decisions.” Cloud Connect Summit zeros in at the most pressing cloud technology, policy and organizational decisions & debates for the cloud-enabled enterprise. Cloud Connect Summit is geared towards a cross-element of disciplines with a stake within the cloud-enabled enterprise. Register for Cloud Connect Summit today.
More Insights