Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

Multi-tenancy in SaaS – Different needs

Posted on: 07 July '11

Many technical analysts and experts define SaaS as a shared code based, multi-tenant application hosted in a data center. Some go on to stress that multi-tenancy is a must in the SaaS world, while some argue that it is just a technical decision.

Is it multi-tenancy that differentiates SaaS from other hosted solutions? Many blogs/discussions and questions still persist! But the real question is – who needs multi-tenancy? Is it the application vendors, service providers, architects or customers? Do SaaS customers relate to it? Let us look at different teams and their ‘view’ of multi-tenancy.

  • Engineering: A group of geeks working behind-the-scenes to develop the application, the way it looks and behaves. Do they need multi-tenancy? It can be argued, but the answer is ‘Yes!’ To manage a single code base with so many tenants’ data, multi-tenancy is easily the best solution that the engineering team can prescribe. Though it has its own challenges to deal with, as any change or defect can affect all the customers and can create a wider impact, but a discipline and a defined methodology can overcome these easily.
  • Operations: Okay, so the Engineering team has built a good scalable solution with an optimized code base to work with all the tenants. The Operations team is happy that they will not have to host different tenants on different servers, which will make their life easier. But then, if there is an issue with the instance or the database, they will have a huge task in hand to ensure that the system doesn’t go down because it if does, it impacts all the customers. Further, they need to manage on-boarding of a new tenant which demands special care as data privacy needs to be maintained. But then, these are just the kind of jobs the Operations team loves and they are outright methodical in what they do. Once documented, a guideline is all they will need.
  • Sales: Now that we have developed a good multi-tenant SaaS solution with great looks and feel, the Sales team can go out in the market to sell. Probably the first few customers will be SMEs (Small & Medium Enterprises) or start-ups that are cost conscious. Then along come the big fishes and they have a lot of questions regarding the solution like where the server is hosted, how sanitized will their data be, who they will be sharing their instance with, what redundancy have been built into system, and so on. Initial reaction from the sales team is bound to be: “Wait a minute! These are technical questions that I shouldn’t be answering!” Wrong! The Sales team needs to understand what lies beneath the hood and what happens behind the scenes so that they can answer these questions comfortably.
  • Customer: Agreed that initial setup and on-boarding is a breeze – a very cost effective way to start using a product without getting into overheads of who will manage it. But there are some questions from the Legal team that need to be answered. Is the application provider in compliance with the regulations? Since I share my data with other tenants, is my data safe from contamination? Can there be an instance only for me as my business does not allow me to share the instance? What guarantees do I get from the service provider? The list grows, but so does SaaS! Some amount of customer education and understanding is needed here.
  • Business: “So, I have a great product which is multi-tasking for me while serving many customers but I can’t afford to put all eggs in the same basket, can I?” Business then talks to Operations and decides to bring in redundancy. They may decide to distribute the tenants across instances. In some cases tenants are informed while in other cases they are not, as it may not be relevant to them. While serving them, they may also have to deal with a big customer who doesn’t like ‘sharing’ and in order to continue the business they may decide to go solo for this customer. Will it still be called SaaS? We will handle this discussion in a different forum at a different place; let us go ahead with the original discussion first, as this is impacting the revenue and we are still in SaaS!

While designing a multi-tenant system, all the teams, including customers, have a role to play and have a say. No one wants to maintain a per customer instance, as overheads are too high in the SaaS world. Multi-tenancy may not define SaaS but it definitely does form an important attribute of SaaS. Not only is it good to have, but sometimes it is necessary to have too; otherwise all the benefits of OPEX vs. CAPEX get erased. Talk to your teams; allow the teams to collaborate to come out with the multi-tenant solution that is optimal for your business and product.

Let multi-tenant architecture or SaaS per se, define your team and how they think and operate. Bring in customers; speak to them about your multi-tenancy, make them understand how it works and most importantly how it will be benefitting them. After all, everyone in SaaS needs multi-tenancy; it is just that the needs from multi-tenancy are different.

What do you think?

 

 

  • Scott Hawkins

    so what are some of the standard responses when a customer comes and asks ‘how can I be sure that my data will not accidentally become open to another of your customers?’

    • Scott,

      Multi-tenant architecture has been been around for sometime and there is nothing better than be transparent and get the customer confidence by explaining the validation process and the underlying architecture (high level). A demo can also be provided to gain customer confidence.

      There is not one response that is applicable to all SaaS providers and the response has to be based on the architecture and process followed. During one of the conference I attended, when I asked the same question, there were different responses, such as:

      1. Showing the process of validation
      2. Walkthrough of the test cases related to issue
      3. Explaining the architecture and how it handles it at design level
      4. Generating reports for multiple customer based on inputs provided

      Regards
      Ranjan