> For the complete documentation index, see [llms.txt](https://academy.cegedim.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.cegedim.cloud/databases/redis.md).

# Redis

## Description

Redis which stands for Remote Dictionary Server, is a fast, open source, in-memory, key-value data store.

It provides built-in replication, different levels of on-disk persistence, and provides high availability with [Sentinel](https://redis.io/topics/sentinel).

A [wide range of developer tools for most popular languages](https://redis.io/clients) exists.

{% embed url="<http://redis.io/>" %}

## Platform as a Service

Redis is deployed on site in **cegedim.cloud** data centers.

**cegedim.cloud** guarantees the same level of service as the Compute offer: instance deployment, operational maintenance, flexibility, security and monitoring are all provided by our experts.

Two topologies are available:

* Standalone instance
* Sentinel cluster of 3 instances

Sizing can be configured to suit your needs.

<table data-full-width="false"><thead><tr><th width="267"></th><th width="237">Standalone</th><th>Cluster</th></tr></thead><tbody><tr><td>Instance(s)</td><td>1</td><td>3</td></tr><tr><td>CPU (per instance)</td><td>2 - 16 vCPU</td><td>2 - 16 vCPU</td></tr><tr><td>RAM (per instance)</td><td>4 - 384 GB</td><td>4 - 384 GB</td></tr><tr><td>Supported version(s)</td><td><ul><li>6.2</li><li>7.2</li></ul></td><td><ul><li>6.2</li><li>7.2</li></ul></td></tr><tr><td>TLS/SSL</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td></tr><tr><td>Monitoring</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td></tr><tr><td>24x7 Monitoring</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td></tr><tr><td>Backup</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td></tr><tr><td>Data replication (DRP)</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Option</td></tr><tr><td>Availability</td><td>99.8%</td><td>99.9%</td></tr><tr><td>Multi-AZ deployment</td><td><span data-gb-custom-inline data-tag="emoji" data-code="274c">❌</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Self-service</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr></tbody></table>

The Sentinel cluster topology is production-ready, with 3 instances distributed across all the Availability Zones in a target Area.

Each instance runs the Redis and Sentinel processes. One instance is primary and the other two are replicas.

For more information, please visit [Redis - Features](/databases/redis/redis-features.md).

## Billing

Billing is processed monthly and based on the number of nodes, plus additional costs for storage, backup and 24/7 monitoring.

Cost estimates for Redis are available via your Service Delivery Manager.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.cegedim.cloud/databases/redis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.