有大量数据库的问题吗? [英] Problem having lots of databases?

问题描述

我们已经构建了一个托管Web应用程序，该应用程序的开发方式是将每个客户都连接到一个单独的数据库.该应用程序是一个Web平台/发布系统，到目前为止，在此设计中一直运行良好.我们还有一个主数据库.

We have built a hosted web application, that is developed in a way that each customer is connected to an individual database. This application is a web plattform/publishing system, and has been working very well so far with this design. We also have a main database.

现在，我们将对定价模型进行一些更改，从而引入免费帐户. (应该)会产生更多的帐户.

Now we are about to make some changes in our pricing model, which would introduce free accounts. This should (hopefully) generate a lot of more accounts.

拥有大量数据库(例如成千上万)(目前约有20个)是否存在问题?有很多优点:分离带来的安全性，可伸缩性，轻松提取客户特定数据(也是可伸缩性的一部分)等.

Is there a problem having a lot of databases, say many thousands (currently about twenty)? There are lots of advantages: security by separation, scalability, easily extract customer specific data (part of scalability too), etc.

推荐答案

尽管可能没有确凿的证据"支持，但我可以理解有关安心和可伸缩性的论点.诸如表更改之类的维护任务可以轻松实现自动化.数据库错误或闯入将被包含在一个客户中，而将数据库移到另一台服务器上则可以轻而易举地完成.

I can understand the arguments about peace of mind and scalability, even though there may no hard "evidence" to support it. Maintenance tasks like table changes could be easily automated. Database errors or break-ins would be contained to one customer, and moving a database to a different server could be done in a breeze.

另一方面，对该模型的批评者可能有一点.

On the other hand, the critics of the model may have a point.

为什么不简单地尝试呢?设置一个单独的凭据系统，将您的数据库复制10.000次，并查看开销和性能是否还可以.

Why not simply try it? Set up a separate credentials system, replicate your database 10.000 times, and see whether overhead and performance are still o.k.

这篇关于有大量数据库的问题吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！