redis
tool judged 0% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2024-W19 | 1 | 1 |
| 2025-W18 | 1 | 1 |
| 2026-W09 | 2 | 1 |
| 2026-W11 | 5 | 2 |
| 2026-W12 | 1 | 1 |
| 2026-W13 | 1 | 1 |
| 2026-W18 | 1 | 1 |
| 2026-W21 | 1 | 1 |
| 2026-W25 | 1 | 1 |
| 2026-W31 | 1 | 1 |
| 2026-W34 | 2 | 2 |
| 2026-W40 | 7 | 4 |
| 2026-W41 | 2 | 2 |
In their words
ports : - " 8000:8000" environment : - QDRANT_URL=http://qdrant:6333 - OLLAMA_URL=http://ollama:11434 - EMBEDDING_MODEL=bge-large-en-v1.5 - GENERATION_MODEL=llama3.1:8b depends_on : - qdrant - ollama volumes : - ./data:/app/data volumes : qdrant_data : ollama_data : Kubernetes Deployment # k8s/rag-deployment.yaml apiVersion : apps/v1 kind : Deployment metadata : name : rag-api spec : replicas : 3
Sliding window log (Redis sorted sets) C.
It also dropped Redis in favour of in-process queues, for example for notifications.
Enterprise Guardrails and Safety Controls Strict Outbound Token Budget Caps: Enforce tenant-level token bucket limits in Redis to prevent rogue API scripts or prompt injection loops from generating multi-thousand dollar bill shocks.
For agents, that calculus can invert, because a single agent turn writes four things that must agree: the conversation state the tool invocation record (and order) the semantic, episodic and workflow memory facts extracted from the turn the idempotency ledger entry that stops a retry re-executing a paid tool If you decide to split these across data stores—one in Postgres, one in a vector store, an
For long‑context applications storing large prompt fragments in memory or Redis, cache size balloons quickly under high traffic.
I implemented a simple Redis cache with a semantic key.
Not "usually." One boundary, deliberately ordinary stack Next.js + TypeScript at the front, FastAPI + Python behind it, PostgreSQL for state, Redis optional, local filesystem for binaries.