In the Cloud: Multi-Tenant vs. Single Tenant ITSM
August 07, 2013
Kevin Smith
Share this

THINKstrategies conducted a recent survey of 341 IT professionals around the world to determine how Cloud Computing alternatives are affecting the IT Service and Client Management needs of organizations.

Among the many interesting findings from this survey, one in particular stands out: nearly half of the survey respondents verify that their currently installed Service and Client Management solutions – that serve as the backbone of IT organizations – are 5+ years old. As a result, many of these aging systems are being evaluated for major upgrades and/or replacement.

While the vast majority of respondents are deploying on-premise Service and Client Management solutions, the tide is shifting to cloud-based implementations.

And this raises big questions about the pros and cons of multi-tenant vs. single tenant cloud architectures that are increasingly relied upon to deliver Service and Client Management solutions ranging from running help desks and change management requests, to incident response processes, service catalogs and, in some cases, ITIL best practices.

The Cons of Single Tenant Cloud Architectures

Let’s examine some distinct disadvantages of single tenant cloud architectures.

For starters, they can only scale out to support new customers in a linear fashion, which means the costs to upgrade individual clients are prohibitive. The downside of this approach is obvious: vendors pass on some of these upgrade costs to customers.

In addition, single-tenant architectures require each customer to maintain a unique software code base that results not only in substantially higher technical support costs but makes software implementations and upgrades much more difficult to deploy than multi-tenant architectures. This approach also limits the frequency of functional upgrades that often times are limited to release cycles once every 12 – 18 months.

Simply put, maintaining multiple versions of an application makes it harder for a Service and Client Management provider to support individual code releases. Why? Technical support staff must be familiar with a broader range of technical issues associated with each release. And junior technical service personnel will often require the assistance of more senior staff as they run across issues that are not familiar with. he typical end result is a significant increase in customer support requests that can create service backlogs. This in turn can erode customer satisfaction levels.

Another drawback of single tenant architectures is that each customer is provided with a dedicated server, which at first blush may appear to be an advantage. However, since data centers charge per server and per virtual machine, each time a customer is added to a single tenant solution, costs to the cloud provider increase. And a portion of those cost increases are, in turn, passed on to the customer.

The Pros of Multi-Tenant Cloud Architectures

On the other hand, cloud-based Service and Client Management solutions based on a multi-tenant architecture maximize organizational efficiency and cost-effectiveness because they operate on an economy-of-scale basis by eliminating the need to expand data center infrastructure linearly. This significantly reduces the overhead associated with providing IT services, and as a result, lowers the costs levied on customers.

In addition, multi-tenant solutions allow software updates to be rolled out to all customers simultaneously. This standardizes software versions utilized by customers. Because each customer maintains the same application and same software version ensured through consistently applied upgrades, they are beneficiaries of more stable software, fewer bug fixes and less disruption to service operations. By eliminating version control issues, support staff can more efficiently respond to maintenance issues resulting in fewer instances of customer service backlogs.

With a multi-tenant architecture, each new customer is put on the same database rather than individual servers, so a provider that offers a multi-tenant solution will lease far less data center equipment compared to a provider offering a single-tenant solution supporting a comparable number of customers. Since each customer does not require its own data center equipment in a multi-tenant environment, the cost of adding customers is fractional compared to a single tenant solution.

The “landlord” analogy helps draw a distinction between single tenant and multi-tenant cloud approaches. Imagine having 100 tenants and you, as landlord, have the option of servicing those tenants in separate homes spread across multiple neighborhoods or in a single high-rise building. The high-rise option is intuitively obvious since you only have to “pay rent” on a single property versus a hundred dwellings and maintenance staff and managers are onsite without having to be dispatched to disparate locations.

While supporters of single tenant architectures will point to perceived security advantages offered by running clients on dedicated servers that don’t “co-mingle” accounts, multi-tenant cloud security advances mitigate this argument.

To quote Jeff Kaplan, Managing Director of THINKstrategies and recognized expert in cloud computing, “Properly designed and administered multi-tenant services can also be even more secure than traditional on-premises product or past ASP arrangements, because the vendor maintains full control of access to its system. In the same way that individual condominium units can be built in a secure fashion with solid walls and strong locks in a shared community, multi-tenant cloud services can also be architected to partition user data and safeguard it against internal and external security threats.”

Like every important choice, there are tradeoffs to consider when making a commitment, especially when it comes to selecting the right cloud architecture. Given the accelerating adoption of cloud computing to support critical IT Service Management functions across organizational business units, there is no substitute for conducting thorough due diligence into the pros and cons of multi-tenant and single tenant cloud options.

ABOUT Kevin Smith

Kevin Smith is responsible for the Cloud Business Unit, including all strategy; go to market and customer success activities for the growing portfolio of FrontRange Cloud applications. Smith has a deep understanding of the Service Management market, having previously been responsible for product management, product marketing and corporate marketing for all FrontRange product lines. Smith brings over 25 years of technical, management, and executive leadership experience in technology and software businesses.

Prior to FrontRange, Smith has held positions as VP of Solutions Management at Manugistics Inc., VP of Operations at Avyx Inc., as well as Flight Design Manager with NASA at the Johnson Space Center in Houston, Texas where he began his career in 1983.

Smith holds a Bachelor of Science in Chemical Engineering from Texas A&M University and a Master of Science in Computer Science from the University of Houston.

Share this

The Latest

October 15, 2019

According to a study by Forrester Research, an enhanced UX design can increase the conversion rate by 400%. If UX has become the ultimate arbiter in determining the success or failure of a product or service, let us first understand what UX is all about ...

October 10, 2019

The requirements of an APM tool are now much more complex than they've ever been. Not only do they need to trace a user transaction across numerous microservices on the same system, but they also need to happen pretty fast ...

October 09, 2019

Performance monitoring is an old problem. As technology has advanced, we've had to evolve how we monitor applications. Initially, performance monitoring largely involved sending ICMP messages to start troubleshooting a down or slow application. Applications have gotten much more complex, so this is no longer enough. Now we need to know not just whether an application is broken, but why it broke. So APM has had to evolve over the years for us to get there. But how did this evolution take place, and what happens next? Let's find out ...

October 08, 2019

There are some IT organizations that are using DevOps methodology but are wary of getting bogged down in ITSM procedures. But without at least some ITSM controls in place, organizations lose their focus on systematic customer engagement, making it harder for them to scale ...

October 07, 2019
OK, I admit it. "Service modeling" is an awkward term, especially when you're trying to frame three rather controversial acronyms in the same overall place: CMDB, CMS and DDM. Nevertheless, that's exactly what we did in EMA's most recent research: <span style="font-style: italic;">Service Modeling in the Age of Cloud and Containers</span>. The goal was to establish a more holistic context for looking at the synergies and differences across all these areas ...
October 03, 2019

If you have deployed a Java application in production, you've probably encountered a situation where the application suddenly starts to take up a large amount of CPU. When this happens, application response becomes sluggish and users begin to complain about slow response. Often the solution to this problem is to restart the application and, lo and behold, the problem goes away — only to reappear a few days later. A key question then is: how to troubleshoot high CPU usage of a Java application? ...

October 02, 2019

Operations are no longer tethered tightly to a main office, as the headquarters-centric model has been retired in favor of a more decentralized enterprise structure. Rather than focus the business around a single location, enterprises are now comprised of a web of remote offices and individuals, where network connectivity has broken down the geographic barriers that in the past limited the availability of talent and resources. Key to the success of the decentralized enterprise model is a new generation of collaboration and communication tools ...

October 01, 2019

To better understand the AI maturity of businesses, Dotscience conducted a survey of 500 industry professionals. Research findings indicate that although enterprises are dedicating significant time and resources towards their AI deployments, many data science and ML teams don't have the adequate tools needed to properly collaborate on, build and deploy AI models efficiently ...

September 30, 2019

Digital transformation, migration to the enterprise cloud and increasing customer demands are creating a surge in IT complexity and the associated costs of managing it. Technical leaders around the world are concerned about the effect this has on IT performance and ultimately, their business according to a new report from Dynatrace, based on an independent global survey of 800 CIOs, Top Challenges for CIOs in a Software-Driven, Hybrid, Multi-Cloud World ...

September 26, 2019

APM tools are your window into your application's performance — its capacity and levels of service. However, traditional APM tools are now struggling due to the mismatch between their specifications and expectations. Modern application architectures are multi-faceted; they contain hybrid components across a variety of on-premise and cloud applications. Modern enterprises often generate data in silos with each outflow having its own data structure. This data comes from several tools over different periods of time. Such diversity in sources, structure, and formats present unique challenges for traditional enterprise tools ...