A Redis client for Rust based on Futures and Tokio that supports PubSub commands, clustered Redis deployments, and more.
With cargo edit.
cargo add fred
Send and Sync wrappers for the client.```rust extern crate fred; extern crate tokio_core; extern crate futures;
use fred::RedisClient; use fred::types::*;
use tokio_core::reactor::Core; use futures::{ Future, Stream };
fn main() { let config = RedisConfig::default();
let mut core = Core::new().unwrap(); let handle = core.handle();
println!("Connecting to {:?}...", config);
let client = RedisClient::new(config); let connection = client.connect(&handle);
let commands = client.onconnect().andthen(|client| { println!("Client connected.");
client.select(0)
}) .and_then(|client| { println!("Selected database.");
client.info(None)
}) .and_then(|(client, info)| { println!("Redis server info: {}", info);
client.get("foo")
}) .and_then(|(client, result)| { println!("Got foo: {:?}", result);
client.set("foo", "bar", Some(Expiration::PX(1000)), Some(SetOptions::NX))
}) .and_then(|(client, result)| { println!("Set 'bar' at 'foo'? {}.", result);
client.quit()
});
let (reason, client) = match core.run(connection.join(commands)) { Ok((r, c)) => (r, c), Err(e) => panic!("Connection closed abruptly: {}", e) };
println!("Connection closed gracefully with error: {:?}", reason); } ```
See examples for more.
Clustered Redis deployments are supported by this module by specifying a RedisConfig::Clustered variant when using connect or connect_with_policy. When creating a clustered configuration only one valid host from the cluster is needed, regardless of how many nodes exist in the cluster. When the client first connects to a node it will use the CLUSTER NODES command to inspect the state of the cluster.
In order to simplify error handling and usage patterns this module caches the state of the cluster in memory and maintains connections to each master node in the cluster. When a command is received the client hashes the key or key hash tag to find the node that should receive the request and then dispatches the request to that node. In the event that a node returns a MOVED or ASK error the client will pause to rebuild the in-memory cluster state. When the local cluster state and new connections have been fully rebuilt the client will begin processing commands again.
This module uses prettyenvlogger for logging. To enable logs use the environment
variable RUST_LOG with a value of trace, debug, error, or info. See the documentation for env_logger for more information.
| Name | Default | Description |
|------|---------|-----------------------------------------------------------------|
| sync | x | Enable the Send and Sync wrappers. |
| fuzz | | Expose the protocol utils as public functions for fuzz testing. |
To run the unit and integration tests:
cargo test -- --test-threads=1
Note a local Redis server must be running on port 6379 and a clustered deployment must be running on ports 30000 - 30005 for the integration tests to pass.
Beware: the tests will periodically run flushall.