> 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/~/revisions/AMiYziCllTKB2y2lmONY/databases/in-memory-db/overview.md).
# Overview
In-Memory DB is a key-value structure-based in-memory data storage. Data is stored in Random-Access Memory (RAM) instead of a disk and is swiftly accessible. Rapid access to data is provided by RAM, as opposed to a disk.
IONOS DBaaS for In-Memory DB is a fully managed service, compatible with legacy Redis® OSS, that gives you access to the capabilities of its data structures. It can be used as a dedicated in-memory cache and a real-time database service. This combination of services enables In-Memory DB to deliver greater performance.
It is simpler to configure your In-Memory DB instance with IONOS DBaaS. You get access to a secure, dedicated In-Memory DB server managed by IONOS. DBaaS gives you access to the capabilities of the In-Memory DB data structures, which means that you can use the same code, applications, and tools you already use in your existing databases. You can use the In-Memory DB features, such as patching the In-Memory DB data structures, creating backups and redundancy, and enhancing security with IONOS DBaaS.
When used as a cache, 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 a caching layer, thus, speeding up the API response time and data retrieval.
In-Memory DB supports data persistence by writing data into long-lasting storage. For more information, see [Data Persistence](/cloud/~/revisions/AMiYziCllTKB2y2lmONY/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 a short, occasional downtime, typically caused by restarting In-Memory DB or switching to another replica.
Provisioning a new In-Memory DB instance via a fully managed IONOS DBaaS is faster than self-managed manual procurement, configuration, and installation of In-Memory DB on local hardware. Software patching and upgrades are performed automatically by DBaaS.
The illustration shows how In-Memory DB instances can be created and managed using IONOS DBaaS.
As shown in the illustration, you can order and manage an In-Memory DB instance using the [API](/cloud/~/revisions/AMiYziCllTKB2y2lmONY/databases/in-memory-db/api-howtos.md). Simultaneously, you can choose the LAN, VDC, and IP address on which In-Memory DB must be available. The IONOS Cloud DBaaS Backend provisions the In-Memory DB instance according to your request. The primary In-Memory DB instance will be available on your LAN within the VDC and on the chosen IP address after provisioning.
## Supported versions
In-Memory DB is compatible with legacy Redis® OSS stable version 7.2.
The IONOS Cloud DBaaS takes care of minor version upgrades during maintenance windows. For more information, see [Upgrade and Maintenance](/cloud/~/revisions/AMiYziCllTKB2y2lmONY/databases/in-memory-db/overview/upgrade-maintenance.md).
## Locations
DBaaS for In-Memory DB is offered in all IONOS Cloud locations. You can use DBaaS instances running In-Memory DB in the IONOS Cloud infrastructure.
## 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 enabling TLS, refer to the [In-Memory DB documentation](https://redis.io/docs/latest/operate/rs/security/encryption/tls/enable-tls/).
---
# 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/~/revisions/AMiYziCllTKB2y2lmONY/databases/in-memory-db/overview.md?ask=&goal=
```
`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.