[英]In mongodb is there a performance reason to separate collections into more than on database?
I have an application using a MongoDB database and am about to add custom analytics. 我有一个使用MongoDB数据库的应用程序,我即将添加自定义分析。 Is there a reason to use a separate database for the analytics or am I better off to build it in the application database? 是否有理由使用单独的数据库进行分析,或者我最好在应用程序数据库中构建它?
Here are the reasons I can think of: 以下是我能想到的原因:
Unless something on this list applies to you, then you don't need to split them out. 除非此列表中的内容适用于您,否则您无需将其拆分。 Also, it's much easier to move a collection across DBs in MongoDB than an RDBMS (as you don't have foreign keys to cause trouble), so IMO it's a relatively easy decision to delay. 另外,在MongoDB中移动集合比在RDBMS中更容易(因为你没有外键导致麻烦),所以IMO是一个相对容易的延迟决定。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.