vendor-documentation · locator & rights
Document database; transactions; replication; sharding
Link and original paraphrase only; upstream rights retained.
Engine / PRODUCT DOSSIER
MCMongoDB Community
Document engine with transactions, replication and sharding.
Investigation: Should web analytics events use a MongoDB time-series collection? →
Self-managed · Source available · SSPL · Community ServerRevision 2026-09-14.1 · unreviewedNeeds recheck · recheck 2026-10-140 attestations · checked 2026-09-14
What we do not know yet · 2 open gaps
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Operator manages the deployment. This target does not include an Atlas service or configured vector-search component.
Applicability, 1 recheck triggers & verification plan
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Operator manages the deployment. This target does not include an Atlas service or configured vector-search component.
Excludes: Runtime verification; Workload benchmarks and cost comparisons; Unlisted extensions, service tiers and deployment configurations
Recheck when
- Upstream version, license, API, service plan or storage topology changes.
Needs recheck · due
Verification plan
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- For vector workloads, measure filtered recall against an exact-search baseline and record index settings.
Provenance & review
Testedknowhow database research
Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.
Revision 2026-09-14.1 · unreviewed · checked
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Document · Engine
Operator manages the deployment. This target does not include an Atlas service or configured vector-search component.
Target sources: MongoDB manual ↗ MongoDB SSPL FAQ ↗
Capability claims · 4 / 17 sourced
Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.
Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.
Data model
Document recordsYes
Explore Document records →
Stores nested document records in collections.
Consistency
Multi-record transactionsYes
Explore Multi-record transactions →
Supports multi-document ACID transactions.
Scope: Requires a supported replica-set or sharded topology; not a standalone-server guarantee.
Operations
ReplicationYes
Explore Replication →
Uses replica sets for replication and failover.
ShardingYes
Explore Sharding →
Distributes documents by shard key.
Unknown · 13 capabilities without evidence
Interface images & local attachments
Sources · 2
vendor-documentation · locator & rights
Community Server licensing
Link and original paraphrase only; upstream rights retained.