Multi-Tenant Cloud vs. Single-Tenant Cloud: An Important Choice
When adopting the cloud, the question isn't public or private — it's single-tenant or multi-tenant. Here is how to plan for your use case.
Join the DZone community and get the full member experience.Join For Free
Whenever we discuss cloud adoption with enterprise companies curious about making the move, one of the first questions is, which is better: public cloud or private cloud? Cloud adopters want to know which approach is most likely to give them better performance, greater flexibility, stronger security, and lowest cost to operate.
While these are important requirements, they miss a critical issue: So you want to share your cloud with others? If you’re working towards an effective cloud adoption strategy, you’d be wise to consider whether you want a multi-tenant or single-tenant cloud offering.
Public vs. Private Cloud: Nothing New to See Here
Plenty has been written about the differences between public and private cloud, so no need to rehash it here. Some of the most popular public cloud offerings are provided by Amazon Web Services (AWS), IBM Cloud, Microsoft Azure, and Google Cloud Platform (GCP). These providers host, in their own data centers, the necessary computing resources that allow you to fire up servers, databases, and other resources to run your applications and websites in the “cloud.” In a public cloud, the provider hosts these resources on an infrastructure shared with other cloud consumers.
Private clouds, on the other hand, are hosted by consumers on-premise, or in data centers owned by third-parties that offer private cloud hosting, such as IBM Cloud Private. Private clouds give the consumer much more control over their infrastructure by providing cloud resources in a personal environment unique to that specific consumer.
Multi-Tenant vs. Single-Tenant Cloud: Something to Think About
In our conversations with cloud adopters, it’s not that uncommon to hear people say they don’t fully trust the security of public clouds, or that they much prefer the control available with private cloud offerings. But just as important as trust or control is rationalizing whether you can afford to share your cloud with another consumer.
Almost all public cloud offerings are multi-tenant, meaning that your websites or applications are hosted right alongside those of other consumers — on the very same servers. In such cases, it’s critical to understand how the provider ensures security and performance, and how you can best manage data latency, throughput, and storage.
If you host your own private cloud, or use a third-party private cloud offering, it’s almost definitely a single-tenant instance, meaning you’re the only consumer with access to it, and the aforementioned concerns of security, performance, and data management are mostly yours to plan and control.
Given the recent security concerns raised by the Meltdown vulnerability, you may worry about sharing a public cloud server, but cloud providers work tirelessly to patch such vulnerabilities as quickly as possible. If you’re hosting your own single-tenant private cloud, vulnerabilities like Meltdown and Spectre are yours alone to mitigate.
Address Your Needs
There’s obviously more than one model for cloud adoption, as customers have to balance many variables. A small slice of a multi-tenant public cloud may work for a startup today, but perhaps not as it grows its services and customer base. Enterprise companies will need to carefully weigh the costs and advantages of sharing multi-tenant or using their own single-tenant cloud.
If you’re a consumer of cloud resources — or planning to become one — you need to ask the right questions when planning your cloud adoption or managing your cloud strategy. Is the most important question for you public cloud vs. private cloud, or is it multi-tenant cloud vs. single-tenant cloud? Are you more concerned with security, performance, or control? Understanding your priorities is the key to making the best, most-informed cloud-adoption decisions.
Published at DZone with permission of Lee Atchison, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.