Managed Document Databases - Concepts
Access Control List (ACL) rules define permissions for remote access to an Instance. A rule consists of an IP address or an IP range. You can use them to define which host and networks can connect to your Database Instance’s endpoint. You can add, edit or delete rules from your ACLs. The initial setup of a Database Instance allows full network access from anywhere (
Access control is handled directly at network level by Load Balancers, making the filtering more efficient, universal and relieving the Database Instance from this task.
Database Instances have settings that allow you to tune the behavior of their database engine to better fit your needs. Available settings depend on the database engine and its version. Each Database Instance setting entry has a default value that the user can override. The deletion of a setting entry restores the setting to the entry’s default value. Some of the default values can be different from the engine’s default, as their configuration is optimized to work at full potential with the Scaleway ecosystem.
Allows you to create a full copy of your Database Instance (including users and permissions) at a point in time. This new Instance is fully independent of its parent.
A Snapshot is a consistent, instantaneous copy of the Block Storage volume of your Database Instance at a certain point in time. They are designed to recover your data in case of failure or accidental alterations of the data by a user. They allow you to quickly create a new Instance from a previous state of your database, regardless of the size of the volume. Snapshots can only be stored in the same location as the original data.
A point of connection to a database. The endpoint is associated with an IPv4 address and a port, and determines whether the endpoint is read-write or not.
A database engine is the software component that stores and retrieves your data from a database. Currently, FerretDB 1.2.0 is available. It runs on PostgreSQL 14.8. Users do not have direct access to the PostgreSQL layer when using FerretDB.
High Availability is a Database Instance configuration that allows you to create a standby node, with an up-to-date replica of the database. If the main node fails for any reason, the standby can take over requests, reducing downtime.
The HA standby node is linked to the main node, using synchronous replication. Synchronous replication offers the ability to confirm that all changes intended by a transaction have been transferred and applied to the synchronous replica node, providing durability to the data.
You can upgrade a standalone node to High Availability after Database Instance creation, but not the opposite.
HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use Read Replicas.
A Database Instance is made up of multiple (at least 1) dedicated compute nodes, and is running a single Database Engine. Exactly one database engine is running on each node.
Logs can contain useful information for debugging or to know more about the behavior and activity of your databases.
Compared to traditional database management, which requires customers to provision their infrastructure and resources to manage their databases, managed databases offer the user access to a Database Instance without setting up the hardware or configuring the software.
A Read Replica is a live copy of a Database Instance that behaves like an Instance, but that only allows read-only connections. The replica mirrors the data of the primary Database node and any changes made are synchronized and reflected in the replica.
Region and Availability Zone
A region is a geographical area such as France (Paris:
fr-par) or the Netherlands (Amsterdam:
nl-ams) in which Scaleway products and resources are located. It can contain multiple Availability Zones.
An Availability Zone refers to the geographical location within a region, such as
waw-1 (Warsaw, Poland), in which your Scaleway resource will be created. The latency between multiple AZs of the same region is low, as they have a common network layer.
For an extensive list of which regions and AZ a resource is available in, refer to our Product availability guide.
Document databases enable users to store and retrieve data in a document format, such as json. Compared to traditional relational databases where data is stored in a table-like format, document-type storage supports storing multiple nested keys and values in each document key.