图I’m continuing on my 行话破坏任务.

今天’s target: “multi-tenancy”‘ and it’据称是次等的兄弟姐妹,“single-tenancy”

What do they mean, and why should 您 care? I’我将首先从以下方面来回答该问题的第二部分“you”成为SaaS创业公司,然后从客户的角度出发。

它是什么?

Desktop software was designed to be installed on 您r computer and only accessed by 您 and therefore only contain 您r data. So 您 are the single tenant. The only person living in that application/database. This is single tenancy.

该软件’s designed from the ground up for the web is designed to be used by lots of people. One application/database, but lots of people using it. (for the techies amongst 您, I really do mean one database, not one instance of a SQL server but with multiple databases running in it). This is 多租户.

It does seem that 单租户 comes in two flavours: one set of code for the application (ie, one set of files serving the app), but multiple databases OR multiple sets of code as well as multiple databases. The former being only half as evil as the latter.

Why should 您 (a SaaS startup) care?

If 您’re not using the 多租户 model 您’再也无法获得一半的收益 SaaS商业模式.

Would 您 rather have just one database/set of files to maintain, or one db/set of files for each individual user?

When it comes to support issues, do 您 want to have to consider whether or not the user has the most recent version of everything in their personal installation or would 您 rather everyone had the exact same thing?

When 您 have to roll out an upgrade, would 您 rather one single schema/file set to update or one for each individual customer.

和这里’最大的一点是:基础设施…

So 您 can get lots of installations on one server. Let’s be generous and assume one server can support 1000 instances of of 您r application and database. Customer 1001 is going to cost 您 a fortune as 您 will need to bring on a new server for it.

随着客户群的增加,硬件成本(无论是租赁还是购买)的增长迅速,维护它们的时间成本也在增加。使用多租户模型,您无需’没有这个问题。我们’单个服务器的成本产生了每月10万英镑以上的收入(成千上万的用户)<每月£1k。你可以’不能使用单租户模型来做到这一点。

Why should 您 (a customer) care?

那’s simple – it costs the vendor a lot more to run a 单租户 model. Guess who, ultimately, is going to cover that extra cost? And when 您 have support issues, 您’re going to get them resolved much faster (for all the reasons stated above) by a 多租户 vendor than a singe-tenancy one.

我没有’t choose to rhyme, rhyming 选择了 me

您会发现许多基于Web的应用程序具有单租户的安排。软件供应商提供了完整的原因清单,“chose”这种模式,但事实是他们没有’选择它。他们提出了建立模型后的原因清单(或“architecture”(我们喜欢这样称呼)为他们决定。

他们强加这种模型的最常见原因是,他们首先采用了专为台式机设计的产品,然后又努力尝试将其用于网络。该公司没有’不知道整个SaaS内容是否会普及,这是一场赌博。因此,为了最大程度地降低风险,他们决定不从头开始编写应用程序,而是使用已有的应用程序。

他们将脚趾浸入水中的一种短视且便宜的方法。

See how 卡什流works with 您r business and 您r books