Considering the Role of a Private IaaS
Why would a company choose to implement a private version of IaaS? There are two compelling reasons:
The company sees itself as a service provider to its employees and partners.
The company needs to control access because of security concerns.
So, a company selecting a private approach creates a pool of resources that can be standardized and easily reused by the IT organization to complete projects. Why standardize? In an IaaS service, IT projects are created in predictable ways. For example, a process might be designed to set up a test environment for code or provision storage to support an application. While certain nuances are different, 80 percent of the time the process within IaaS can be standardized. By standardizing these infrastructure services, the organization gains efficiencies, fewer inadvertent errors, and consistency in managing the development lifecycle. This is the same approach used by a public IaaS vendor to control its costs.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
