List of FerretDB terminologies
This section contains a list of common terminologies related to FerretDB.
A way of processing documents in a collection and passing them through various operations or stages. See list of supported aggregation operations and commands here.
A set of operators that lets you perform complex operations that aggregate and summarize values. See list of supported aggregation pipeline operators here.
The telemetry service of FerretDB. See telemetry for more details.
BSON is a serialized binary file format for storing JSON-like documents.
The list of types that the BSON format supports.
BSON offers support for additional data types compared to JSON, such as
A group of documents in a non-relational database. It is comparable to a table in a relational database.
The four basic operations of a database: Create, Read, Update, and Delete. See Basic FerretDB CRUD operations here.
An organized repository for collections containing its own sets of documents, and data.
The set of commands in FerretDB. For more information, see supported commands for more details.
A record in a collection that comprises key-value pairs. See Documents for more.
Dot notation is used to reference or access the elements in an array or in an embedded document. See dot notation for more details.
Similar to columns in a relational database. They are represented as field name-value pairs and describe the kind of data in a document.
A data structure used for identifying and querying records in a collection.
It helps to limit the number of documents to search through or inspect in a collection.
_id index, user-defined index, hashed index, and partial index.
See Indexes for more.
JSONB is a data type of PostgreSQL that stores JSON data as a decomposed binary format.
A defining 12-byte type that ensures singularity and uniques within a collection and are used to represent the default values for the
A keyword that starts with a
$ character to query, update, or transform data.
FerretDB utilizes operation modes to define its approach in handling incoming requests, serving purposes such as testing, debugging, and bug reporting.
By default, FerretDB operates in
See Operation modes for more details.
An immutable identifier for a record.
The primary key of a documents is stored in the
_id field, which typically contains the
Proxy is any MongoDB-compatible database that is running in parallel with FerretDB. It's used to test differences between FerretDB and other databases. See Operation modes for more details.
An open source relational database. FerretDB uses PostgreSQL as a database engine.
SQLite is a self-contained, serverless system ideal for lightweight applications. FerretDB now offers SQLite backend support.