John R. Rymer serves Application Development & Delivery Professionals. See the full Analyst bio.
Visit Forrester.com to learn how we make Application Development & Delivery Professionals successful every day.
Follow John on Twitter.
John R. Rymer serves Application Development & Delivery Professionals. See the full Analyst bio.
Visit Forrester.com to learn how we make Application Development & Delivery Professionals successful every day.
Follow John on Twitter.
Posted by John R. Rymer on November 26, 2012
James Staten and I wrote this vision of the future of cloud computing. The full report is available to Forrester clients at this link. The research is part of Forrester’s playbook to advise CIOs on productive use of cloud computing and is relevant to application development and delivery leaders as well.
This research charts the shifts taking place in the market as indicated by the most advanced cloud developers and consumers. In the future, look for the popular software-as-a-service (SaaS) and infrastructure-as-a-service (IaaS) models to become much more flexible by allowing greater customization and integration. Look for more pragmatic cloud development platforms that cross the traditional cloud service boundaries of SaaS, platform-as-a-service (PaaS), and IaaS. And look for good private and public cloud options — and simpler ways of integrating private-public hybrids.
The key takeaways from this research are:
A key finding of our research is emergence of a new model for cloud platforms. We call this model IaaS-Plus and cite Amazon Web Services as the primary example. There are now two major kinds of cloud platforms: IaaS-Plus and platform-as-a-service (PaaS).
In the IaaS-Plus model, developers have greater operating system, middleware, and database choice than they do with PaaS, greater ability to configure IaaS resources, as well as OS, middleware, and database than they have with PaaS, as well as access to mix-and-match application services.
Amazon Web Services is by far the most popular cloud platform, and we expect high adoption of other IaaS-Plus offerings as other vendors join the category. Microsoft and Google, for example, recently added IaaS-Plus options to their cloud platforms, which previously were PaaS only. Will PaaS die? No, but neither will the PaaS model dominate.
The table below briefly compares IaaS-Plus and PaaS.
|
|
Cloud Platform Model |
|
|
|
IaaS-Plus |
PaaS |
|
Platform services |
VMs, native services |
Containers, native services |
|
Access to IaaS layer |
Yes |
No |
|
Access to middleware config |
Yes |
No |
|
Access to database config |
Yes |
No |
|
Choice of operating system |
Yes |
No |
|
Provides development tools |
No |
Usually yes |
|
Provides a complete platform |
Usually no |
Usually yes |
Other key findings:
What it means: It is time for CIOs to assemble their plans to consume, manage, offer, and secure cloud services and platforms – with the emphasis on public services. This means creating new career paths for your key IT leaders, getting them the experience and training they need to make this transition successfully, and embracing the services that will be the foundation for this new, more diverse portfolio now.
Our research incorporates findings from Forrester’s Q3 2012 Global Cloud Developer Online Survey. Find a summary of that survey’s findings here.
Comments
Service Catalog Myths
I think the use of service catalogs by a cloud service provider makes every senses. It is just a bridge to far for many traditional IT organizations. Why? because you have to have a robust understanding of what represents a service and how it needs to be packaged and marketed to each target audience. Product Management 101 thinking and skillset. This tends to be missing from many IT organizations.
Connecting the catalog to the service portfolio concept as described by ITIL again is a straightforward step for those who's business is service provision. But for mainstream IT organizations it introduces yet another obstacle, suggesting a path that is fraught with risk, and unexpected costs.
Just think, IT would have to possibly reorganize and shift their infrastructure farming culture to one that is focused on what customers need to be successful, a profit and loss driven portfolio management system, service requests and all the backend workflow response, and then a service catalog.
Then again, if cloud providers are likely to do much of this lifting as part of their normal business operations, it might make sense to outsource the service catalog development project :-)
Post new comment