IaaS enables greater control of IT infrastructure within an organization. Characteristically, IaaS models have cost structures that are problematic to forecast and manage. On the other hand, PaaS has a cost structure that can be more carefully managed. Although PaaS is making inroads and is expected to grow relative to IaaS in the future, some organizations will choose control over cost.
IaaS billing can be also be problematic, despite its pay-as-you-go model. Cloud billing is tremendously granular and broken down to echo the exact usage of services. Cost breakdowns for every resource and service involved in an application deployment can add up quickly.
Because IaaS cloud service providers own the infrastructure, the precise details of configuration and performance in the infrastructure are mostly unclear to the customer. This lack of transparency can make systems management and monitoring more complex.
Finally, the availability and performance of the workloads are highly dependent on the cloud service provider. If the IaaS provider experiences network blockages or any form of downtime, internal or external, the customer is affected. And because IaaS is a multitenant architecture, a gluttonous neighbor can negatively impact workloads as well.
In the end, it all comes down to which service best fits the organization’s specific project or future plans. Infrastructure as a Service (IaaS) is just one of a growing number of cloud service provider models to diversify provider offerings and cut waste from data management.