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

# Redis

Frends offers seamless integration with [Redis](https://redis.io/), enabling you to effortlessly connect and automate data flows involving Redis for caching, messaging, and real-time data management.

Frends provides tasks for performing all core Redis operations.

By leveraging Frends' task-based approach, you can configure and customize Redis integrations according to your specific requirements. Frends offers a wide range of tasks that facilitate integrations to a variety of systems and protocols.

## Use cases

Below you will find typical use cases for Redis integrations and how they are implemented in Frends.

### Caching frequently accessed data

Use Frends tasks to store and retrieve frequently used data in Redis, reducing load on backend systems and improving performance.

<figure><img src="/files/qIGKqBdasRteMVtVfwmR" alt=""><figcaption><p>Caching data</p></figcaption></figure>

### Managing keys in a database

With Frends tasks, you can manage your keys in Redis Database, simplifying workload on database management

<figure><img src="/files/JY0sxzy9ayDba9vf1ZaT" alt=""><figcaption><p>Manage</p></figcaption></figure>


---

# 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.frends.com/tasks/tasks/redis.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.