Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-582

Explain benefits of splitting schemas across collections and databases

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Trivial - P5 Trivial - P5
    • Server_Docs_20231030
    • 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.

            Assignee:
            sam.kleinman Sam Kleinman (Inactive)
            Reporter:
            jmikola@mongodb.com Jeremy Mikola
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              11 years, 33 weeks, 4 days ago