Driver compatibility matrix (Java/Node/Python/.NET/Go)
Parent: MongoDB Upgrade Paths · Published reference · snapshot 2026-10-22 · skill mongodb-cohort-2a03c480ee30
↓ Facts as markdownall context files
Source-anchored research for Driver compatibility matrix (Java/Node/Python/.NET/Go). Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Problems, failure modes and limitations
- Driver/server incompatibility has a protocol boundary: MongoDB's SDAM specification requires a driver to mark a topology incompatible and set a compatibility error when the server and client wire-version ranges do not overlap. The compatibility table separately distinguishes a partial feature set from a connection incompatibility or an untested combination. (high confidence) [source]
Facts and statements
- MongoDB publishes separate compatibility tables for client-driver versions against MongoDB Server versions and against the driver language or runtime. Its server table covers Java, Node.js, PyMongo, .NET/C#, and Go, and marks full support (✓), partial support (⊛), incompatibility (✗), and untested combinations (blank). (high confidence) [source]
- As of 2026-10-14, MongoDB's matrix marks Java Sync 5.12–5.13, Node.js 7.6–7.7, PyMongo 4.18, .NET/C# 3.10–3.12, and Go 2.9 fully compatible with MongoDB Server 9.0. MongoDB separately advises confirming that the driver supports the target server version before upgrading. (medium confidence) (verified as of 2026-10-14) [source]
- MongoDB states that driver and server version numbers advance independently, so matching similar version numbers does not establish compatibility. Before a major production upgrade, MongoDB recommends confirming driver support and testing the application; Percona independently recommends testing the new server version and verifying driver compatibility. (high confidence) [source]
- Atlas's Connect documentation requires a Node.js driver that supports MongoDB 7.0 or later to connect to a Free M0 or Flex cluster. This makes driver/server compatibility an access prerequisite for those cluster products. (medium confidence) (verified as of 2026-10-14) [source]
- Atlas's SLA covers officially supported MongoDB drivers at current versions. Atlas gives best-effort support for end-of-life official drivers and diagnosis-only, best-effort support for community drivers, so an older driver can remain technically compatible while losing the current support level. (high confidence) (verified as of 2026-10-14) [source]
- Driver compatibility rules are service-specific. AWS says a MongoDB driver used with Amazon DocumentDB 8.0 must be compatible with MongoDB 5.0 or later, and AWS documents functional differences for DocumentDB. The MongoDB Server compatibility matrix therefore should not be treated as a feature-parity guarantee for another MongoDB-compatible service. (medium confidence) (verified as of 2026-10-22) [source]
- MongoDB defines ✓ as all features supported, ⊛ as a driver that works but lacks some new server features, ✗ as a driver that will not work, and a blank cell as untested. A partial row therefore does not guarantee access to every new server feature, and an unmarked cell is not confirmed incompatibility. (low confidence) [source]
- Mongoose's compatibility guide says Mongoose uses the MongoDB Node.js Driver and separately lists Mongoose version ranges for MongoDB Server releases. Applications using an ODM should check its compatibility range in addition to the native driver matrix. (medium confidence) [source]
- Inference from the MongoDB matrix's scope: a fully compatible driver/server mark describes compatibility with a MongoDB Server release. It does not establish that an Atlas tier exposes a feature or determine tier pricing; check Atlas feature and tier documentation for those decisions. (medium confidence) [source]
- The unofficial driver-compatibility checker README describes an automated check based on driver releases and a three-year server-EOL window. Use it as a candidate filter, then confirm each pairing in MongoDB's official matrix, which exposes full, partial, incompatible, or untested status and runtime details. (medium confidence) [source]
Children
- No children recorded.