Share this post:
There is no doubt that cloud brings us an entire new set of value propositions for enterprise computing environments, offering a huge set of benefits like application scalability, operational flexibility, improved economies of scale, reduced costs, resource efficiencies, agility improvement and more. It is harder to find all these benefits when considering just the traditional computing model.
Generally speaking, organizations today can choose between two types of clouds. Traditional clouds offer virtual machines (VMs) that are extremely easy to use but abstract disk, memory and CPU and come with a performance penalty. Bare metal clouds are essentially physical servers that can be deployed on demand and billed hourly.
When I first heard about bare metal in a cloud context, all of a sudden a question came up in my mind: From a conceptual perspective, does a cloud configuration require some kind of virtualization?
In fact, the National Institute of Standards and Technology (NIST), whose cloud computing definition is widely accepted in the industry, omits virtualization as a criterion for cloud. The essential characteristics mentioned by NIST include on-demand self-service, broad network access, resource pooling, rapid elasticity and measured service, but not virtualization. This may surprise many in the IT community (like me!) who have always assumed that a virtualized server infrastructure was necessary to provide the flexibility and scalability associated with cloud.
With that said, you can see that VMs are great for some things and bare-metal servers are great for other things. Sometimes those reasons are technology and sometimes those reasons are based in finance issues.
You should consider VM cloud for highly dynamic workloads where you’re not really worried about performance. For example, if you have an application that spins up and down rapidly, or if you have very temporary workloads that must be spun up in minutes and run for a short period of time before you turn them off, virtualization is great.
But if your application is sensitive to performance, bare metal can be unbeatable. Bare metal cloud services refer to a type of high-performance, hosted-server offering that combines the advantages of traditional dedicated servers with those of infrastructure as a service (IaaS) virtual servers.
With bare metal cloud, all of the resources of physical servers are dedicated to a single user and can offer better performance than a comparable virtualized server. Because resources are not being shared, no hypervisor layer is needed, allowing more of the server’s processing power to be allocated to the application.
Some of the advantages of bare metal cloud services are:
• Resources dedicated to a single customer
• Greater processing power and input/output operations per second (IOPS)
• More consistent disk and network I/O performance
• Quality of Service (QoS) that guarantees elimination of the noisy neighbor problem in a multitenant environment.
Another benefit from bare metal is security. The potential of breaking regulatory compliance in a multitenant environment was the main reason why security-sensitive organizations were originally reluctant to move their data to the cloud. With bare-metal servers, it is possible to implement physical segregation of resources.
Another important issue addressed by bare metal is that there are some software vendors with license and support agreements that don’t support sub-capacity license models. In this case, the vendor does not allow the use of soft partitioning as a means to determine or limit the number of software licenses required for any given server.
You will have to pay for the software license as if you are using the entire physical server, even if you are not.
As you can see, there is not a correct answer for the question in the title of the post. It will always depend on the type of workload you need to run on top of the cloud.
I would like to hear from you. Which cloud would you choose and why?