A lightweight implementation of Redis Streams for Rust, allowing you to manage streaming messages in a simplified way. With redsumer you can:
To use redsumer from GitHub repository with specific version, set the dependency in Cargo.toml file as follows:
[dependencies]
redsumer = { git = "https://github.com/enerBit/redsumer-rs.git", package = "redsumer", version = "0.4.2" }
You can depend on it via cargo by adding the following dependency to your Cargo.toml
file:
[dependencies]
redsumer = { version = "0.4.2" }
Create a new producer instance and produce a new stream message from a BTreeMap:
use std::collections::BTreeMap;
use redsumer::*;
use time::OffsetDateTime;
use uuid::Uuid;
#[tokio::main]
async fn main() {
let credentials: Option<ClientCredentials> = None;
let host: &str = "localhost";
let port: &str = "6379";
let db: &str = "0";
let stream_name: &str = "my-stream";
let producer_result: RedsumerResult<RedsumerProducer> =
RedsumerProducer::new(
credentials,
host,
port,
db,
stream_name,
);
let producer: RedsumerProducer = producer_result.unwrap_or_else(|error| {
panic!("Error creating a new RedsumerProducer instance: {:?}", error);
});
let mut message: BTreeMap<&str, String> = BTreeMap::new();
message.insert("id", Uuid::default().to_string());
message.insert("started_at", OffsetDateTime::now_utc().to_string());
let id: Id = producer.produce(message).await.unwrap_or_else(|error| {
panic!("Error producing stream message from BTreeMap: {:?}", error.to_string());
});
}
Similar to the previous example, you can produce a message from a HashMap or a HashSet. Go to examples directory to see more use cases like producing a stream message from an instance of a struct.
The produce method accepts a generic type that implements the ToRedisArgs trait. Take a look at the documentation for more information.
Create a new consumer instance and consume messages from stream:
use redsumer::*;
use redsumer::redis::StreamId;
#[tokio::main]
async fn main() {
let credentials: Option<ClientCredentials> = None;
let host: &str = "localhost";
let port: &str = "6379";
let db: &str = "0";
let stream_name: &str = "my-stream";
let group_name: &str = "group-name";
let consumer_name: &str = "consumer";
let since_id: &str = "0-0";
let min_idle_time_milliseconds: usize = 1000;
let new_messages_count: usize = 3;
let pending_messages_count: usize = 2;
let claimed_messages_count: usize = 1;
let block: u8 = 5;
let consumer_result: RedsumerResult<RedsumerConsumer> = RedsumerConsumer::new(
credentials,
host,
port,
db,
stream_name,
group_name,
consumer_name,
since_id,
min_idle_time_milliseconds,
new_messages_count,
pending_messages_count,
claimed_messages_count,
block,
);
let mut consumer: RedsumerConsumer = consumer_result.unwrap_or_else(|error| {
panic!("Error creating a new RedsumerConsumer instance: {:?}", error);
});
loop {
let messages: Vec<StreamId> = consumer.consume().await.unwrap_or_else(|error| {
panic!("Error consuming messages from stream: {:?}", error);
});
for message in messages {
if consumer.is_still_mine(&message.id).unwrap_or_else(|error| {
panic!(
"Error checking if message is still in consumer pending list: {:?}", error
);
}) {
// Process message ...
println!("Processing message: {:?}", message);
// ...
let ack: bool = consumer.ack(&message.id).await.unwrap_or_else(|error| {
panic!("Error acknowledging message: {:?}", error);
});
if ack {
println!("Message acknowledged: {:?}", message);
}
}
}
}
}
In this example, the consume method is called in a loop to consume messages from the stream. The consume method returns a vector of StreamId instances. Each StreamId instance represents a message in the stream. The is_still_mine method is used to check if the message is still in the consumer pending list. If it is, the message is processed and then acknowledged using the ack method. The ack method returns a boolean indicating if the message was successfully acknowledged.
The main objective of this message consumption strategy is to minimize the possibility that two or more consumers from the same consumer group operating simultaneously consume the same message at the same time. Knowing that it is a complex problem with no definitive solution, including business logic in the message processing instance will always improve results.
Take a look at the examples directory to see more use cases.
The [redis] module provides utilities from the redis crate. You can use these utilities to interact with Redis values and errors.
The Value enum represents a Redis value. It can be converted to a specific type using the from_redis_value function. This function can be imported from the [redis] module. redsumer includes the [FromRedisValueHandler] struct that implements the FromRedisValue trait for a lot of types. It is useful to convert a Value to a specific type reducing boilerplate code and total lines of code.
We welcome contributions to redsumer-rs
. Here are some ways you can contribute:
Thank you for your interest in improving redsumer-rs
!