MongoDB Developer Associate study materials
MongoDB Developer Associate study resources

MongoDB Developer Associate key terms

MongoDB Developer Associate · Get comfortable with the vocabulary.

BSON

Binary JSON, the serialization format MongoDB uses to store documents on disk and send them over the wire. It extends JSON with types like ObjectId, Date, Decimal128, and binary data.

Related: Document, ObjectId, Decimal128
Document

A single record in MongoDB, written as an ordered set of field-value pairs similar to JSON. Documents are the basic unit of storage and are grouped into collections.

Related: Collection, BSON, Embedded document
Collection

A named group of documents inside a database, roughly analogous to a table in relational systems. Collections do not enforce a fixed schema unless validators are configured.

Related: Document, Schema validation, Database
ObjectId

A 12-byte BSON value used as the default _id: a 4-byte timestamp, 5-byte random process value, and 3-byte counter. It is roughly time-ordered and unique without a central sequence.

Related: _id field, BSON
_id field

The mandatory unique identifier for every document in a collection. MongoDB creates an ObjectId if none is supplied, and a unique index on this field is created automatically.

Related: ObjectId, Unique index
Embedded document

A document nested as the value of a field inside another document. Embedding keeps related data together so it can be read in one query, but nested documents have size limits.

Related: Document, Dot notation, 16 MB document limit
Dot notation

The path syntax using dots to address fields inside embedded documents or arrays, such as address.city or items.price. It is used in queries, projections, updates, and index definitions.

Related: Embedded document, Projection, Update operator
CRUD operations

The four core data operations: create (insertOne, insertMany), read (find, findOne), update (updateOne, updateMany, replaceOne), and delete (deleteOne, deleteMany). Drivers expose them as language-specific methods.

Related: Update operator, Write concern, Read concern
Query filter

The document passed to find or update methods that selects matching records. Fields are matched by equality by default, and comparison, logical, and array operators can refine the selection.

Related: Query operator, Projection, Cursor
Query operator

A $-prefixed keyword such as $gt, $in, $regex, or $elemMatch that expresses conditions beyond simple equality. Operators can be combined with $and, $or, and $nor for complex filters.

Related: Query filter, Dot notation
Projection

A document specifying which fields a query should return, using 1 to include and 0 to exclude. Except for _id, inclusion and exclusion cannot be mixed in the same projection.

Related: Query filter, Covered query
Cursor

An iterator over query results that fetches documents in batches rather than all at once. Drivers expose methods like hasNext and next, and the server closes idle cursors after a timeout.

Related: Batch size, Query filter
Update operator

A $-prefixed instruction such as $set, $unset, $inc, $push, or $pull that modifies specific fields without replacing the whole document. Replacements instead pass a full document without operators.

Related: Upsert, Array operator, CRUD operations
Upsert

An option on update operations that inserts a new document when no record matches the filter. The new document combines equality conditions from the filter with the update operators applied.

Related: Update operator, Write concern
Array operator

An update operator that manipulates array fields, such as $push, $addToSet, $pop, $pull, and $pullAll. Positional $ and arrayFilters let you target specific elements.

Related: Update operator, Dot notation
Aggregation pipeline

A sequence of stages that transforms documents, each stage passing results to the next. Stages like $match, $group, $project, $sort, and $lookup express filtering, reshaping, and joining.

Related: $group stage, $lookup stage, $match stage
$match stage

An aggregation stage that filters documents using the same syntax as a query filter. Placed first, it lets the planner use indexes and reduces work for later stages.

Related: Aggregation pipeline, Query filter, Index
$group stage

An aggregation stage that groups documents by an _id expression and computes accumulators such as $sum, $avg, $min, $max, and $push. It resembles SQL GROUP BY.

Related: Aggregation pipeline, Accumulator
$lookup stage

An aggregation stage that performs a left outer join with another collection in the same database. It matches local fields against foreign fields and adds an array of matched documents.

Related: Aggregation pipeline, Reference
Accumulator

An expression used inside $group or $bucket that computes a value across grouped documents, for example $sum, $avg, or $first. Some accumulators are also usable in $setWindowFields.

Related: $group stage, Aggregation pipeline
Index

A B-tree structure that stores a small portion of collection data in an order that speeds matching and sorting. Without a suitable index, the server must scan every document in the collection.

Related: Compound index, explain(), Collection scan
Compound index

An index on multiple fields whose key order matters for both equality and sort. The prefix rule means a query can use the index only if it filters on a leading portion of the keys.

Related: Index, Index prefix, Multikey index
Index prefix

A leading subset of a compound index's fields that a query can use on its own. For an index on {a:1, b:1, c:1}, queries on a or on a and b can use it efficiently.

Related: Compound index, explain()
Multikey index

An index on an array field that creates entries for each element, allowing queries on array contents. A compound index can include at most one array field.

Related: Index, Compound index
Unique index

An index that rejects inserts and updates producing duplicate key values. The _id index is always unique, and a unique index on other fields enforces a business rule.

Related: Index, _id field, Duplicate key error
explain()

A method that reports how the query planner executes a query, including the winning plan, stages used, documents examined, and whether an index was applied.

Related: Index, Collection scan, Query planner
Collection scan

A query execution strategy that examines every document because no usable index exists. It appears as a COLLSCAN stage in explain output and usually signals a missing index.

Related: Index, explain()
Replica set

A group of mongod processes maintaining the same data, with one primary accepting writes and secondaries replicating its oplog. Failover elects a new primary if the current one becomes unavailable.

Related: Oplog, Write concern, Read preference
Oplog

The capped collection on each replica set member that records every write in an idempotent form. Secondaries tail it to apply changes, and its size bounds how long a member can be offline.

Related: Replica set, Write concern
Write concern

A setting that specifies how many replica set members must acknowledge a write before it returns, such as w:1 or w:"majority". It trades durability for latency.

Related: Replica set, Read concern, Read preference
Read concern

A setting controlling the consistency of data returned by a read, such as local or majority. Higher levels may return older but more durable data from a replica set.

Related: Write concern, Read preference, Replica set
Read preference

A client setting that chooses which replica set members serve reads, such as primary, secondary, or nearest. It affects latency and freshness but not write routing.

Related: Replica set, Read concern
Schema validation

Optional per-collection rules using JSON Schema or query expressions that reject documents not matching the declared shape. Validation can be applied on insert and update with configurable strictness.

Related: Collection, Document
16 MB document limit

The maximum size of a single BSON document, which constrains how much data can be embedded. Data exceeding it must be split across documents or stored in GridFS.

Related: Embedded document, GridFS
GridFS

A specification for storing files larger than the document size limit by splitting them into chunks across two collections. Drivers provide APIs for reading and writing these files.

Related: 16 MB document limit, BSON
Reference

A pattern where a document stores the _id of a related document instead of embedding it. References avoid duplication but require a second query or a $lookup to resolve.

Related: Embedded document, $lookup stage
MongoClient

The driver object that manages a connection pool to a deployment and is created once per application. From it, applications obtain databases and collections for operations.

Related: Connection string, Connection pool
Connection string

A URI such as mongodb://host:27017/db that tells a driver where to connect and which options to apply. It can list multiple hosts for a replica set or use the mongodb+srv scheme.

Related: MongoClient, Connection pool
Connection pool

A driver-managed set of reusable sockets to the server, sized by options like maxPoolSize. Reusing connections avoids handshake overhead and bounds concurrency.

Related: MongoClient, Connection string
Duplicate key error

The error raised when a write violates a unique index, reported with code 11000. Drivers surface it as an exception or rejected promise that applications must handle.

Related: Unique index, Write concern