> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/databases/in-memory-db/overview.md).

# Overview

In-Memory DB is a key-value structure-based in-memory data store, based on [<mark style="color:blue;">Valkey</mark>](https://valkey.io/). Data is stored in Random-Access Memory (RAM) instead of on disk, providing rapid access to data.

<code class="expression">space.vars.ionos\_cloud</code> DBaaS for In-Memory DB is a fully managed service, compatible with legacy Redis® OSS, giving you access to the capabilities of its data structures. It can be used as a dedicated in-memory data store and a real-time database service.

When used as an in-memory data store, In-Memory DB accelerates data access from primary instances and associated data stores with minimal latency. This is quicker as compared to interacting with a traditional database. In-Memory DB acts as an in-memory data layer, speeding up the API response time while improving data retrieval.

In-Memory DB supports data persistence by writing data into long-lasting storage. For more information, see [<mark style="color:blue;">Data Persistence</mark>](/cloud/databases/in-memory-db/overview/data-persistence.md).

It is mandatory to specify a periodic maintenance time window for regular maintenance. During the maintenance time window, you may encounter short, occasional downtime. This is typically caused by restarting In-Memory DB or switching to another replica.

The illustration shows how a client requests an In-Memory DB cluster through the DCD or API, which the <code class="expression">space.vars.ionos\_cloud</code> DBaaS System provisions into a Virtual Data Center (VDC): a primary node plus one or more secondary nodes, connected over the datacenter's LAN.

![Diagram showing a user creating an In-Memory DB instance through the DCD or API; the DBaaS System provisions it into a VDC containing a primary node and secondary nodes connected over the LAN](/files/o8B0PUIF6hXNZM7IvIet)

You can order and manage an In-Memory DB cluster through the [<mark style="color:blue;">DCD</mark>](/cloud/databases/in-memory-db/how-tos.md) or the [<mark style="color:blue;">API</mark>](/cloud/databases/in-memory-db/api.md). You choose the LAN, VDC, and IP address on which In-Memory DB is available. The <code class="expression">space.vars.ionos\_cloud</code> DBaaS System provisions the cluster according to your request; the primary instance becomes available on your chosen LAN, VDC, and IP address once provisioning completes.

## Supported versions

In-Memory DB supports the following Valkey versions:

| Version | Status    |
| ------- | --------- |
| 9       | Supported |
| 8.1     | Supported |
| 8       | Supported |

The <code class="expression">space.vars.ionos\_cloud</code> DBaaS takes care of minor version upgrades during maintenance windows. For more information, see [<mark style="color:blue;">Upgrade and Maintenance</mark>](/cloud/databases/in-memory-db/overview/upgrade-maintenance.md).

## Locations

DBaaS for In-Memory DB is available in the following locations:

| **Data Center**           | **Region** |
| ------------------------- | ---------- |
| Berlin, Germany           | `de-txl`   |
| Frankfurt, Germany        | `de-fra`   |
| Paris, France             | `fr-par`   |
| Logroño, Spain            | `es-vit`   |
| London, United Kingdom    | `gb-lhr`   |
| Worcester, United Kingdom | `gb-bhx`   |
| Las Vegas, United States  | `us-las`   |
| Lenexa, United States     | `us-mci`   |
| Newark, United States     | `us-ewr`   |

## Security

The communication between clients and In-Memory DB is secured using TLS for secure data transmission if your In-Memory DB is set up to use it. For more information about activating TLS, refer to the [<mark style="color:blue;">In-Memory DB documentation</mark>](https://valkey.io/topics/encryption/).

You get access to all command categories except those listed in the "dangerous" category. For more information, refer to the [<mark style="color:blue;">In-Memory DB documentation</mark>](https://valkey.io/topics/acl/#command-categories).

## Platform tasks

### What does IONOS CLOUD manage for In-Memory DB?

<code class="expression">space.vars.ionos\_cloud</code> handles all back-end tasks necessary to keep your In-Memory DB cluster operating at peak efficiency:

* Database management through the DCD or the DBaaS API.
* Regular patches and upgrades during maintenance windows.
* Automated snapshots or backups, depending on your cluster version, for disaster recovery.
* Service monitoring, both for the In-Memory DB cluster and the underlying infrastructure.

### What remains my responsibility?

Tasks related to the optimal health of your In-Memory DB cluster remain your responsibility, including optimization, organizing data, and updating statistics.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/databases/in-memory-db/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.