Managed Database for Redis™ - Concepts
Access control list (ACL) rules define permissions for remote access to a Database Instance. A rule consists of an IP address or an IP range.
A Redis™ cluster consists of a set of primary and secondary nodes. The cluster nodes use hash partitioning to split the keyspace into 16,384 key slots. Each primary of the cluster is responsible for a subset of those slots. Each secondary node replicates the data of one of the primary ones.
Each Managed Database for Redis™ cluster consists of minimum three and maximum six compute Instances hosting each a primary Redis™ Instance and a secondary Instance for one of the other nodes. If one of the primary nodes fails, the remaining nodes hold a vote and elect one of the remaining secondary nodes as the new primary node. When the failing node rejoins the cluster, it automatically becomes a secondary node and begins to replicate the data of another primary node.
An endpoint is a point of connection to a database. The endpoint is associated with one or more public IPv4 addresses and a port, or with a private IPv4 and a port (if you use Private Networks).
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.
High Availability is handled through the Redis™ clustering feature. This is a 3-node multi-master architecture. In case of downtime on a node in the cluster, a new node is able to take over the requests with minimal downtime.
A feature that allows you to increase the size of your Redis™ Database Instance infrastructure by adding more nodes to your Database Instance to increase your number of endpoints and distribute cache.
A database management system primarily built upon memory. Data is managed and stored within the main memory of an Instance. This allows the optimization of request speed and the improvement of application performance.
Compared to traditional database management, which requires customers to provision their own infrastructure and resources to manage their databases, Managed Databases offer the user access to a Database Instance without them needing to set up the hardware or configure the software.
A configuration directive used to set the maximum amount of memory Redis™ can use for a data set. You can set this value via the Scaleway console or by configuring the
available_settings via API.
Region and Availability Zone
A Region is as 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 Products availability guide
TCP Keep alive
A packet that is sent by a device when the TCP connection on a routing device has been idle for too long. The packet is sent to the peer with only the Acknowledgement flag (ACK) turned on.
Transport Layer Security (TLS) is an Internet security protocol that enables data to be securely exchanged over a network using in transit encryption.
Feature that allows you to increase the size of your Redis™ Database Instance by upgrading to a bigger node type to allow increased traffic for the same endpoint.