Concepts¶
adk-redis maps Google ADK service interfaces onto Redis, the Agent Memory
Server, and RedisVL. These pages explain the what and why behind each
feature. For step-by-step setup instructions, see the
User Guide.
There are four ways to use this integration. Pick the page that matches your goal.
-
Architecture diagram and the ADK interfaces this package implements.
-
Framework-managed sessions and memory. The ADK Runner handles everything automatically.
-
LLM-controlled memory via MCP or REST-based tools. The agent decides when to remember and recall.
-
Vector, hybrid, range, text, and SQL search over your own data via in-process tools or MCP.
-
Skip repeat LLM calls with self-hosted (RedisVL) or managed (LangCache) semantic caching.
Where to Start¶
| Goal | Read this |
|---|---|
| Understand the big picture | ADK overview |
| Let the framework manage sessions and memory | Sessions + Memory Services |
| Give the LLM explicit memory tools | Sessions + Memory MCP + Tools |
| Search your own knowledge base | RedisVL MCP + Search Tools |
| Reduce LLM latency and cost | Semantic Caching |
| Get a working agent running | Quickstart |
| Run and test your agent | ADK runtime |