Infrastructure-as-a-service (IaaS) has gained traction with organisations that want to speed up the deployment of IT and lower the total cost of ownership for IT assets. As companies progress further on their IaaS journey, they should consider adopting a platform-as-a-service (PaaS) model. Here's why.
Cloud computing diagram image from Shutterstock
According to VMware Advisory Services strategist Brian Martinez, while IaaS focuses on rolling out infrastructure quickly and conveniently, it doesn't add direct value to a business. The value comes from deploying applications faster and building services around those applications.
So you have IaaS, what’s next? Enter the concept of PaaS. PaaS can be realised in a variety of ways. It might be through second generation platforms such as database-as-a-service or middleware-as-a-service. Or it could be via third generation platforms based on unstructured PaaS like containers (think Docker) or structured PaaS (think Pivotal Cloud Foundry).
You can be flexible on how you want your PaaS strategy to look like but Martinez suggests the best approach is to base it on the needs of the developers in your organisation.
Many times we see strategies built around a tool name instead of the outcomes needed from that tool. Listening to the developer’s needs should help determine what the requirements are. Then build backwards from there. Often we you won’t end up with the same tooling then you thought you would.
You can read more about implementing a PaaS strategy over at the VMware blog.
[Via VMware blog]