There's been a lot of discussion on the Internet about the definition of
Platform-as-a-Service. Here's just a few very active Twitter discussions to
illustrate the level of activity and passion over the topic:
This is just a few of the hundreds of tweets returned when I queried "Paas"
and "definition". The interesting thing is that the sheer breadth of the
discussion makes it very difficult to nail down exactly what it is.
Gartner Group's method of responding to the madness was to develop their own
taxonomy of PaaS, which seems to have been very helpful for them in
organizing their research, but, in contrast to many other things Gartner has
led on defining, their PaaS taxonomy has not really caught on with the cloud
community. The Gartner taxonomy breaks things out based upon the primary
functionality of the platform, such as application development, business
Recent commentaries by cloud industry luminaries Reuven Cohen & Krishnan
Subramanian address key issues related to relative importance and potential
longevity of an independent Platform-as-a-Service (PaaS). In his commentary,
Reuven poses, "Do consumers really care about the difference between IaaS and
PaaS?" The answer to this question is most likely, no, but that doesn't
eliminate the need for distinction, it merely is a matter of how best to
deliver the value of cloud computing to users.
In his commentary, Krishnan does an excellent job of exploring one way to
classify PaaS a... (more)
In the early part of 2013, EMC announced a new storage virtualization product
called ViPR that delivers a software interface to block, object and HDFS
storage services layered on heterogeneous storage. As part of that
announcement there was an architectural discussion regarding how ViPR would
be providing these services to applications that entails breaking out the
design into two components: the control plane and the data plane.
The control plane provides common interfaces for provisioning, policy &
management while the data plane provides interfaces for data access from
To lower IT operational costs and/or to become more agile, the business must
simplify the processes to deliver and manage infrastructure and the
applications running on that infrastructure. Focusing on one without the
other is simply applying yet another band-aid to an already hampered
environment. Delivering IT as a service requires transformative efforts
across all of IT and a re-evaluation of the metrics currently used to judge
success. Achieving these goals demands a new platform and approach to
delivering data and applications to users.
I was recently reviewing a reference ... (more)
I will admit I have been a strong opponent of those listing roles and
organizations as DevOps. Primarily because DevOps is a way to do something
and creating a role DevOps Engineer is just putting lipstick on the pig for
those looking to hire a Linux Sysadmin or infrastructure script coder.
Likewise, the DevOps organization is a somewhat more likeable term, but still
ambiguous at best. It’s either the organization that is helping to redefine
IT by having development and operations individuals work together on the same
team, which is really just IT using a different process and sh... (more)