> 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/use-cases.md). # Use Cases ## Real-time analytics and online advertising campaigns In-Memory DB is suitable for exceptional reliability and swift data retrieval. It stands out as the preferred choice for real-time analytics, offering seamless storage and analysis of streaming data. With its capability to process data with sub-millisecond latency, In-Memory DB significantly enhances the performance of real-time analytics applications and online advertising campaigns. ## Database Caching In-Memory DB excels at managing vast volumes of real-time data through its in-memory data storage mechanism. It efficiently groups data based on different values, such as users, time, roles, and so on, and saves it in your primary database in a single transaction. This can save you time by eliminating the need for thousands of read/write operations, depending on how many queries you receive every minute; thus, facilitating the creation of highly responsive database architectures. Leveraging In-Memory DB for caching minimizes database queries, significantly reducing traffic and the resources needed. This approach enables enhanced application performance, achieving shorter response times. Furthermore, In-Memory DB's scalable caching layer allows for rapid and cost-effective scaling, enabling organizations to develop swift applications with reduced costs. --- # 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://docs.ionos.com/cloud/databases/in-memory-db/use-cases.md?ask=&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.