Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Client comparison

This page compares documented client contracts, not feature counts. A checkmark can hide the questions that matter in production: whether a connection is exclusive or multiplexed, which commands are replayed after reconnect, whether a cache is managed for you, and whether a “typed” API fixes the response type or lets the caller choose one.

The comparison was checked on 2026-09-25 against the versions and revisions below. Links point to upstream documentation or pinned source. Treat a claim as unknown when the cited material does not establish it; do not infer absence from an empty cell.

ClientBaseline used here
redis-tower186719e; published workspace versions range from 0.1.1 to 0.1.3
redis-rs1.7.0 (2a29a8f)
Fred10.1.0 (29d4790)
Lettuce4461844 plus the rolling Lettuce wiki, checked on the date above
go-redis2fc3ccd
StackExchange.Redis0a92ae4
ioredisb597303
node-redisd3eac3d
redis-pyba6976b

Rust clients

redis-tower, redis-rs, and Fred overlap heavily, but expose different contracts.

Contractredis-towerredis-rs 1.7Fred 10.1
Typed command APICommand values fix their response types; pinned Get returns Option<Bytes>. Raw commands can opt into a decoder.AsyncTypedCommands provides typed convenience methods; Cmd::query_async::<T> retains caller-selected conversion.Command traits expose typed arguments and caller-selected response types; see the versioned interfaces module.
Composition pointFrame services implement Tower Service; pinned middleware sources cover timeouts, circuit breaking, tracing, and metrics.Unknown / not compared: the 1.7 API index documents commands and connections, but this review did not establish a general middleware contract.Config and the versioned interfaces are client-specific extension points; no cross-client middleware equivalence is asserted here.
Shared connectionPinned MultiplexedClient is cloneable and auto-pipelines concurrent commands over one connection.MultiplexedConnection is cloneable and multiplexed.Client is a cloneable handle over the driver’s connections.
PoolPinned ConnectionPool owns independent connections with fixed, dynamic, or lazy population and explicit health/lifecycle controls.Optional r2d2 and bb8 integrations are listed in the pinned 1.7 feature definitions. A multiplexed connection is not itself a checkout pool.Pool distributes commands across clients; stateful interfaces are intentionally omitted.
TopologyStandalone, Cluster, and Sentinel are separate clients; pinned UniversalClient provides one enum-backed entry point.Standalone plus the cluster-async and sentinel features are defined in the pinned 1.7 manifest.ServerConfig covers centralized, Cluster, Sentinel, and Unix deployments.
Reconnect and replayPinned ResilientRedisClient single-flights reconnects with bounded backoff. Ordinary in-flight commands are not silently replayed; stateful APIs document their own restoration rules.ConnectionManager reconnects in the background; the command that observes the dropped connection errors and later commands wait for the replacement connection.ReconnectPolicy controls reconnect delay. Fred’s pinned ConnectionConfig defaults to three command attempts, and reconnect_once flushes previously in-flight commands from the retry buffer. The redelivery metric counts requests sent again after close while awaiting a response; pinned command policy and attempt checks show that fail-fast, attempt exhaustion, or no reconnect policy stops redelivery.
Client-side cachingPinned standalone and master-routed Cluster caching manages tracking, invalidations, bounds, metrics, and reconnect fail-closed behavior.The experimental cache-aio feature integrates caching with multiplexed, connection-manager, and async Cluster connections.TrackingInterface exposes RESP3 tracking and invalidation commands; it is not documented as a managed local cache.
Redis Stack and newer familiesPinned redis-tower-modules covers JSON, Search, TimeSeries, Bloom/Cuckoo, and Vector Sets.The pinned 1.7 feature definitions include JSON, Bloom, and Vector Sets; Search is marked unfinished.The versioned interfaces module documents JSON and Search interfaces. Other families remain unverified here.
CredentialsPinned CredentialProvider supports reconnect/push rotation; sibling crates provide AWS IAM and Microsoft Entra providers.The pinned 1.7 feature definitions include token-based authentication and Microsoft Entra support.Versioned Config exposes a credential provider when its feature is enabled.
ObservabilityPinned production guidance documents stable tracing fields, metrics-facade recording, pool/queue snapshots, and bounded opt-in per-node Cluster labels.Unknown / not compared: no client-wide tracing/metrics contract was verified from the 1.7 API index; application wrappers are outside this comparison.Pinned TracingConfig is feature-gated; versioned MetricsInterface exposes redelivery, queue, latency, and payload-size measurements. Export to an external metrics backend remains application work.
RESP behaviorPinned redis-tower-protocol documents RESP2/RESP3 negotiation, push demultiplexing, and explicit rejection of unsupported attributes/streamed aggregates.RESP2 and RESP3 are supported; URL selection is documented by versioned ConnectionInfo.Pinned Config::version defaults to RESP2 and can require RESP3; TrackingInterface requires RESP3 for tracking.

The important typed-API distinction is not “typed versus untyped.” All three clients provide typed conveniences. redis-tower command values own a specific decoder, while redis-rs and Fred also make caller-selected response conversion a common path.

Lessons from widely used clients

These clients are useful design references, not direct feature-score opponents.

ClientDocumented contract worth carrying into a review
LettuceIts execution reliability documentation treats reconnect replay, duplicates, ordering, and transaction behavior as separate guarantees. A generic “reconnects automatically” claim is insufficient.
go-redisThe pinned README documents automatic pooling, experimental streaming credentials, RESP3 client caching limits, and OpenTelemetry instrumentation. Its experimental auto-pipeline warns that retrying a whole batch can duplicate non-idempotent work.
StackExchange.RedisConnectionMultiplexer is designed to be shared and reused; cheap database handles and multiplexing are deliberately different from checking out a socket per request.
ioredisThe pinned README documents standalone, Sentinel, and Cluster connections, offline queues, retry behavior, and auto-pipelining. Queueing before connect and replaying after a disconnect are different decisions.
node-redisIts pinned FAQ says already-sent commands reject when the socket closes because Redis may have executed them; unsent commands can remain queued for reconnect. That boundary is a useful retry model.
redis-pyThe pinned unified response proposal separates wire-protocol shape from the public response contract. Differential tests must normalize client-facing values, not merely compare raw RESP frames.

What this page does not claim

  • It does not rank clients. API fit, deployed topology, language ecosystem, and operational familiarity usually matter more than a total capability count.
  • It does not publish performance conclusions. The repository’s pinned benchmark publication protocol defines workloads, client versions and adapters, topology, connection count, timeouts, metadata, and reproducibility requirements. A result is evidence only for the measured environment and scenario.
  • It does not turn undocumented behavior into “no.” Unknown behavior stays unknown until a stable upstream source or a reproducible experiment supports a narrower statement.

When updating this page, pin the source revision, record the check date, link the precise upstream contract, and describe reconnect, retry, replay, pooling, caching, and response typing independently.