Distributed Cache Service

Distributed Cache Service (DCS)

For e-commerce, video sharing, gaming, and other data-intensive applications, it is essential for data to be retrieved as quickly as possible. Distributed Cache Service (DCS) in the Open Telekom Cloud provides a fast, yet inexpensive data retrieval, allowing you to access data from in-memory data stores instead of relying entirely on slower disk-based databases.

Redis (NoSQL database) is available in the Open Telekom Cloud as DCS. It is ideal for use as a cache server, e.g., in order to accelerate the loading times of websites, and is able to handle various data structures. Clusters made up of individual DCS instances can be used for applications with extremely high performance requirements. DCS in the Open Telekom Cloud is billed on an hourly basis is accordance with the chosen RAM size and type (master/standby or single-node database).

Reasons for DCS in the Open Telekom Cloud

Icon clock with arrow in clockwise direction

Backing Up and Restoring

If a DCS instance becomes faulty, data in the instance can be restored from an OBS backup so that service continuity remains unaffected.

Learn more

Icon with folders and puzzle in background

Command Capability with Redis

DCS supports compatibility with Redis commands, including supported commands, disabled commands, unsupported scripts, commands of later Redis versions, and restrictions on command usage.

Learn more

Icon with hooks and folders in background

Reliability

Data persistence, support for master/standby and Proxy Cluster modes, and automatic failover between cache nodes ensure data reliability and service availability.

DCS Specifications

Single-node DCS Redis 3.0 instances

For each single-node DCS Redis instance, the available memory is less than the total memory, because some memory is reserved for system overhead, as shown in the table below.

Total Memory	Available Memory	Maximum Allowed Connections	Assured/Maximum Bandwidth
2 GB	1.5 GB	10,000	42/512 Mbit/s
4 GB	3.2 GB	10,000	64/1,536 Mbit/s
8 GB	6.8 GB	10,000	64/1,536 Mbit/s
16 GB	13.6 GB	10,000	85/3,072 Mbit/s
32 GB	27.2 GB	10,000	85/3,072 Mbit/s
64 GB	58.2 GB	12,000	128/5,120 Mbit/s

Master/standby DCS Redis 3.0 instances

For each master/standby DCS Redis instance, the available memory is less than that of a single-node DCS Redis instance, because some memory is reserved for the data persistence, as shown in the table below. The available memory of a master/standby instance can be adjusted to support background tasks such as data persistence and master/standby synchronization.

Total Memory	Available Memory	Maximum Allowed Connections	Assured/Maximum Bandwidth
2 GB	1.5 GB	10,000	42/512 Mbit/s
4 GB	3.2 GB	10,000	64/1,536 Mbit/s
8 GB	6.4 GB	10,000	64/1,536 Mbit/s
16 GB	12.8 GB	10,000	85/3,072 Mbit/s
32 GB	25.6 GB	10,000	85/3,072 Mbit/s
64 GB	51.2 GB	12,000	128/5,120 Mbit/s

Proxy Cluster DCS Redis 3.0 instances

In addition to larger memory, Proxy Cluster instances feature more connections allowed and higher bandwidth allowed than single-node and master/standby instances as shown in the table below.

Total Memory	Available Memory	Maximum Connections Allowed	Assured/Maximum Bandwidth
64 GB	64 GB	90,000	600/5,120 Mbit/s
128 GB	128 GB	180,000	600/5,120 Mbit/s
256 GB	256 GB	240,000	600/5,120 Mbit/s
512 GB	512 GB	480,000	600/5,120 Mbit/s

DCS for Redis 4.0

DCS for Redis 4.0 is developed based on Redis 4.0.14 and is compatible with open-source protocols and commands.

Commands Supported by DCS for Redis 4.0 are:

Table 1 and Table 2 list the Redis commands supported by DCS Redis 4.0 instances.
Table 3 and Table 4 list the Redis commands supported by Proxy Cluster DCS Redis 4.0 instances.
Table 5 and Table 6 list the Redis commands supported by read/write splitting DCS Redis 4.0 instances.DCS für Redis 4.0 wurde auf der Grundlage von Redis 4.0.14 entwickelt und ist mit Open-Source-Protokollen und -Befehlen kompatibel.

Table 1 - Commands supported by DCS Redis 4.0 instances

Table 1 Von DCS Redis 4.0-Instanzen unterstützte Befehle (1)

Table 2 - Commands supported by DCS Redis 4.0 instances

Table 2 Von DCS Redis 4.0-Instanzen unterstützte Befehle (2)

Table 3 - Commands supported by Proxy Cluster DCS Redis 4.0 instances

Table 3 Von Proxy Cluster DCS Redis 4.0-Instanzen unterstützte Befehle (1)

Table 4 - Commands supported by Proxy Cluster DCS Redis 4.0 instances

Table 4 Von Proxy Cluster DCS Redis 4.0-Instanzen unterstützte Befehle (2)

Table 5 - Commands supported by read/write splitting DCS Redis 4.0 instances

Table 5 Befehle, die von DCS Redis 4.0-Instanzen mit Lese-/Schreibzugriff unterstützt werden (1)

Table 6 - Commands supported by read/write splitting DCS Redis 4.0 instances

Table 6 Befehle, die von DCS Redis 4.0-Instanzen mit Lese-/Schreibzugriff unterstützt werden (2)

DCS for Redis 5.0

DCS for Redis 5.0 is developed based on Redis 5.0.9 and is compatible with open-source protocols and commands.

Commands Supported by DCS for Redis 5.0 are:

Table 1 and Table 2 list commands supported by DCS for Redis 5.0.
Table 3 and Table 4 list commands supported by Proxy Cluster DCS for Redis 5.0 instances.
Table 5 and Table 6 list the Redis commands supported by read/write splitting DCS Redis 5.0 instances.

Table 1- Commands supported by DCS Redis 5.0 instances (1)

Table 1 Von DCS Redis 5.0-Instanzen unterstützte Befehle (1)

Table 2 - Commands supported by DCS Redis 5.0 instances (2)

Table 2 Von DCS Redis 5.0-Instanzen unterstützte Befehle (2)

Table 3 - Commands supported by Proxy Cluster DCS Redis 5.0 instances (1)

Table 3 Von Proxy Cluster DCS Redis 5.0-Instanzen unterstützte Befehle (1)

Table 4 - Commands supported by Proxy Cluster DCS Redis 5.0 instances (2)

Table 4 Von Proxy Cluster DCS Redis 5.0-Instanzen unterstützte Befehle (2)

Table 5 - Commands supported by read/write splitting DCS Redis 5.0 instances (1)

Table 5 Befehle, die von DCS Redis 5.0-Instanzen mit Lese-/Schreibzugriff unterstützt werden (1)

Table 6 - Commands supported by read/write splitting DCS Redis 5.0 instances (2)

Table 6 Befehle, die von DCS Redis 5.0-Instanzen mit Lese-/Schreibzugriff unterstützt werden (2)

Redis commands disabled for security reasons in DCS 4.0 and 5.0

For security purposes, some Redis commands are disabled in DCS 4.0 and 5.0 as follow.

Redis 4.0

Table 1 Redis commands disabled in single-node and master/standby Redis 4.0 instances

Table 2 Redis commands disabled in Proxy Cluster DCS Redis 4.0 instances

Tabelle 2 Redis-Befehle, die in Proxy Cluster DCS Redis 4.0-Instanzen deaktiviert sind

Table 3 Redis commands disabled in Redis Cluster DCS Redis 4.0 instances

Tabelle 3 - Redis-Befehle in Redis Cluster DCS Redis 4.0-Instanzen deaktiviert

Table 4 Redis commands disabled in read/write splitting DCS Redis 4.0 instances

Tabelle 4 Redis-Befehle, die bei DCS Redis 4.0-Instanzen mit Lese-/Schreibzugriff deaktiviert sind

Redis 5.0

Table 1 Redis commands disabled in single-node and master/standby Redis 5.0 instances

Tabelle 1 Redis-Befehle, die in Single-Node- und Master/Standby-Redis-5.0-Instanzen deaktiviert sind

Table 2 Redis commands disabled in Proxy Cluster DCS Redis 5.0 instances

Tabelle 2 Redis-Befehle, die in Proxy Cluster DCS Redis 5.0-Instanzen deaktiviert sind

Table 3 Redis commands disabled in Redis Cluster DCS Redis 5.0 instances

Tabelle 3 Redis-Befehle in Redis Cluster DCS Redis 5.0-Instanzen deaktiviert

Table 4 Redis commands disabled in read/write splitting DCS Redis 5.0 instances

Tabelle 4 Redis-Befehle, die in DCS Redis 5.0-Instanzen mit Lese-/Schreibaufteilung deaktiviert sind

Use Cases

DCS instances are fully managed, meaning you no longer need to perform management tasks such as hardware provisioning, software patching, monitoring, or failure recovery. The service can handle various data structures, but should not be used for complex ones - relational databases are better suited for these purposes.

Caching storage in RAM allows fast data access, meaning Redis as DCS is ideal for use as a cache server for all applications in which speed is the main focus, such as real-time analyses, high-speed transactions, and message queuing. However, the storage cache is not persistent, meaning that the stored data is deleted if the virtual machine is switched off. Consider using DCS when you need to cache the following types of data:

Web Pages
Caching the content of web pages improves page load times. The cached content can include static data, such as HTML pages, CSS, and images.
Status
DCS provides quick and simple queries of session status and application-scaling status, enabling easy sharing of status information.
Application objects
DCS serves as a level-2 cache at the service layer and provides data storage and access for external entities. Storing frequently requested data in DCS instances can offload databases and reduce access latency.
Events
DCS provides continuous event querying, allowing streams of events to be processed as they occur.

New Features

08/01/2019Status Dashboard expandedView Details

07/15/2022New DCS versions 4.0 and 5.0 for Redis Cache Engine availableView Details

08/22/2022DCS versions 4.0 and 5.0 for Redis Cache Engine available in NLView Details

Bekijk alle Release Notes

Find out more

Bestel nu en ontvang starttegoed ter waarde van € 250* (code: 4UOTC250)

Book now

Profiteer van ons adviesaanbod!
Gratis en deskundig.

Wij beantwoorden je vragen over de testmogelijkheid, boeking en het gebruik – gratis en persoonlijk. Probeer het uit!

088 447777(tijdens kantooruren)

+800 33044770internationale hotline (24/7)

Stuur een e-mail

* Voucher is inwisselbaar tot 31.12.2023. Neem contact met ons op voor het bedrag van de voucher bij de boeking. Het kortingsvolume is alleen geldig voor klanten met een factuuradres in Duitsland en vervalt 2 maanden na het afsluiten van het contract. Het tegoed wordt verrekend met de geldige catalogusprijzen volgens de servicebeschrijving. Een uitbetaling is uitgesloten.