SaaS数据库设计 - 多个数据库?分裂? [英] SaaS database design - Multiple Databases? Split?
本文介绍了SaaS数据库设计 - 多个数据库?分裂?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
解决方案
从一个数据库开始。
以下是我们可以从LinkedIn学习的内容:
- 单个数据库不起作用
- 参照完整性将无法进行
- 任何数据丢失都是一个问题
- 即使适度有效,缓存也很好
- 不要低估增长轨迹
来源:
I've seen SaaS applications hosted in many different ways. Is it a good idea to split features and modules across multiple databases? For example, putting things like the User table on one DB and feature/app specific tables on another DB and perhaps other commonly shared tables in another DB?
解决方案
Start with one database. Split data/functionality when project requires it.
Here is what we can learn from LinkedIn:
- A single database does not work
- Referential integrity will not be possible
- Any data loss is a problem
- Caching is good even when it's modestly effective
- Never underestimate growth trajectory
Source:
LinkedIn communication architecture
这篇关于SaaS数据库设计 - 多个数据库?分裂?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文