{"id":"jumpserver-redis","name":"redis","af_score":44.8,"security_score":58.5,"reliability_score":46.2,"what_it_does":"Redis is an in-memory data store and key-value database that also supports data structures (e.g., strings, hashes, lists, sets, sorted sets), persistence options, pub/sub, and common caching/queue patterns. It can be used standalone or as part of larger architectures.","best_when":"You need low-latency reads/writes and flexible data structures for caching, coordination, or real-time features, and you can manage persistence, replication, and operational risk appropriately.","avoid_when":"You cannot ensure network isolation and secure configuration (auth/TLS), or you need strict transactional guarantees and relational query capabilities.","last_evaluated":"2026-04-04T21:34:10.954267+00:00","has_mcp":false,"has_api":false,"auth_methods":["Redis AUTH (password)","TLS client authentication (mTLS) if configured at the server/proxy layer","Network-level controls (VPC/security groups, allowlists)"],"has_free_tier":false,"known_gotchas":["Redis is not an HTTP API; agent integrations often assume REST semantics (status codes, retries) that do not directly apply.","Idempotency varies by command; many write commands are not inherently idempotent.","Operational issues (timeouts, connection drops) need command-level retry/backoff policies managed by the client.","Misconfiguration can expose Redis publicly; ensure auth/TLS and network restrictions."],"error_quality":0.0}