5 releases (3 breaking)
0.5.1 | Jun 22, 2023 |
---|---|
0.5.0 | Feb 26, 2023 |
0.3.0 | Jan 5, 2023 |
0.2.0 | Dec 25, 2022 |
0.1.0 | Dec 25, 2022 |
#1034 in Concurrency
30 downloads per month
Used in 5 crates
(3 directly)
64KB
1K
SLoC
An actor-like RPC framework built for true zero-copy message handling.
A actor-like RPC framework built for true zero-copy message handling.
This framework is inspired by tonic but is not a GRPC framework. Instead, it makes use of the incredible rkyv (de)serialization framework which provides us with lightning fast (de)serialization and also lets us perform true zero-copy deserialization which can lead to massive performance improvements when processing lots of big messages at once.
Features
- Fast (de)serialization of owned types.
- True zero-copy deserialization avoiding heavy allocations.
- Dynamic adding and removing of message handlers/services.
Basic example
use std::net::SocketAddr;
use datacake_rpc::{
Channel,
Handler,
Request,
RpcClient,
RpcService,
Server,
ServiceRegistry,
Status,
};
use rkyv::{Archive, Deserialize, Serialize};
// The framework accepts any messages which implement `Archive` and `Serialize` along
// with the archived values implementing `CheckBytes` from the `bytecheck` crate.
// This is to ensure safe, validated deserialization of the values.
//
// Checkout rkyv for more information!
#[repr(C)]
#[derive(Serialize, Deserialize, Archive, PartialEq, Debug)]
#[archive(compare(PartialEq), check_bytes)]
#[archive_attr(derive(PartialEq, Debug))]
pub struct MyMessage {
name: String,
age: u32,
}
pub struct MyService;
impl RpcService for MyService {
// The `register_handlers` is used to mark messages as something
// the given service can handle and process.
//
// Messages which are not registered will not be dispatched to the handler.
fn register_handlers(registry: &mut ServiceRegistry<Self>) {
registry.add_handler::<MyMessage>();
}
}
#[datacake_rpc::async_trait]
impl Handler<MyMessage> for MyService {
type Reply = String;
// Our `Request` gives us a zero-copy view to our message, this doesn't actually
// allocate the message type.
async fn on_message(&self, msg: Request<MyMessage>) -> Result<Self::Reply, Status> {
Ok(msg.to_owned().unwrap().name)
}
}
#[tokio::main]
async fn main() -> anyhow::Result<()> {
let address = "127.0.0.1:8000".parse::<SocketAddr>()?;
let server = Server::listen(address).await?;
// Services can be added and removed at runtime once the server is started.
server.add_service(MyService);
println!("Listening to address {}!", address);
// Channels are cheap to clone similar to tonic.
let client = Channel::connect(address);
println!("Connected to address {}!", address);
let rpc_client = RpcClient::<MyService>::new(client);
let msg1 = MyMessage {
name: "Bobby".to_string(),
age: 12,
};
// Clients only need references to the message which helps
// reduce allocations.
let resp = rpc_client.send(&msg1).await?;
assert_eq!(resp, msg1.name);
Ok(())
}
Dependencies
~6–14MB
~165K SLoC