#redis #multiplexing #connection #notifications #command #kubernetes #reconnection


Redis multiplexing with reconnection notifications and MGET auto-batching

21 unstable releases (10 breaking)

0.12.1 May 21, 2024
0.12.0 Mar 24, 2024
0.11.0 Mar 16, 2024
0.9.0 Jun 11, 2023
0.1.0 Nov 30, 2021

#487 in Database interfaces

Used in 3 crates

MIT license

555 lines


License Cargo Documentation

Redis multiplexing with reconnection notifications and MGET auto-batching

Why use this instead of redis::aio::ConnectionManager?

  • Error-free reconnection behavior: when a command would otherwise fail as a consequence of the connection being dropped, this library will immediately reconnect and retry when able without producing an otherwise avoidable IoError and with subsequent reconnections debounced 1500ms
  • ENV configuration simplifies kubernetes usage
  • Reconnects can be observed allowing for Redis server-assisted client-side caching using client tracking redirection
  • Integrated MGET auto-batching

ENV Configuration

Composible connection urls are provided by environment variables using env-url with the REDIS prefix:

# Override env mapping for easy kubernetes config


use redis::{AsyncCommands, RedisResult};
use redis_swapplex::get_connection;

async fn get_value(key: &str) -> RedisResult<String> {
  let mut conn = get_connection();

Runtime Configuration (optional)

For best performance, use the Tokio runtime as configured via the tokio::main or tokio::test macro with the crate attribute set to async_local while the barrier-protected-runtime feature is enabled on async-local. Doing so configures the Tokio runtime with a barrier that rendezvous runtime worker threads during shutdown in a way that ensures tasks never outlive thread local data owned by runtime worker threads and obviates the need for Box::leak as a means of lifetime extension.


~570K SLoC