Home > Uncategorized > Multi-tenancy Architecture

Multi-tenancy Architecture

April 9th, 2010

This is a good opinion piece on why multi-tenancy matters as an architecture choice for SaaS providers.


From the customer perspective, it’s really a long-term investment issue. If you’re going to invest time and energy in effectively using a piece of SaaS software, you want to know that there’s going to be future functionality updates and competitive pricing that will keep pace with your business.

In some cases, this isn’t a concern – the selected SaaS solution might just be for the short term, though anyone in IT knows the big gap between how long something is expected to be in service, and how long you actually use it for. Remember those Y2K app issues?

So the theory is that if you have a true multi-tenant solution you can manage your operations and service more effectively. I think that’s true, but usually, it’s more about the people and processes than technology, so I’m sure there will be examples that prove us wrong either way.

Categories: Uncategorized Tags:
  1. April 26th, 2010 at 15:17 | #1

    I know everyone talk about the advantage of SaaS is that you can use a SaaS application for the short term and then move on to another SaaS vendor at anytime. However, it’s been my experience that this does not happen very often. The time and money spent training people on using the application and creating the interfaces usually make companies think twice about switching. I am a big believer in true multi-tenancy. It forces the SaaS provider to keep their customers on one codeline (hopefully to keep costs down for everyone) and forces customers to accept the enhancements on a regular basis so that they don’t get too far behind.

Comments are closed.