-
Type: Task
-
Resolution: Duplicate
-
Priority: Trivial - P5
-
Affects Version/s: None
-
Component/s: manual
-
Labels:None
The question of when to use multiple databases or collections for schema design comes up frequently in free and paid support channels. It would probably make a worthwhile FAQ or manual entry to explain the benefits of creating schemas across multiple collections or databases to deal with limits of padding factors, fragmentation, and concurrency.
Basically, summarize when it makes sense to break a schema across multiple collections or databases, with notes against premature optimization.
- duplicates
-
DOCS-414 FAQ: With the advent of 2.2 and db-level locking, what are the implications of having one collection per database?
- Closed