[DOCS-582] Explain benefits of splitting schemas across collections and databases Created: 07/Oct/12 Updated: 30/Oct/23 Resolved: 06/Nov/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Jeremy Mikola | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 11 years, 19 weeks, 4 days ago | ||||||||||||
| Description |
|
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. |