remoc
A Rust library for remote multiplexed objects, channels, and RPC over various transports.
What is remoc?
Remoc is a Rust library that enables seamless communication between distributed components through remote objects, channels, and remote procedure calls (RPC). It provides a type-safe, multiplexed transport layer that works over TCP, TLS, WebSockets, and other protocols, making it ideal for building distributed systems, microservices, and networked applications.
Rust developers building distributed systems, microservices, or networked applications that require type-safe, multiplexed communication between components.
Developers choose Remoc for its emphasis on type safety, performance, and flexibility, allowing them to build robust distributed systems without sacrificing Rust's guarantees, with built-in support for secure connections and multiplexing to reduce overhead.
Overview
Remoc 🦑 — Remote multiplexed objects, channels and RPC for Rust
Use Cases
Best For
- Building distributed systems with type-safe remote object sharing and interaction.
- Implementing microservices that require secure, multiplexed RPC with streaming responses.
- Developing networked applications needing bidirectional channels with backpressure support.
- Creating systems that require transport flexibility over TCP, TLS, or WebSockets.
- Establishing secure connections with TLS and optional authentication in distributed environments.
- Reducing network overhead by multiplexing multiple logical streams over a single physical connection.
Not Ideal For
- Systems requiring seamless interoperability with non-Rust components, as Remoc is Rust-centric and lacks built-in cross-language support.
- Applications where ultra-low latency is critical, as serialization overhead and multiplexing can introduce measurable delays.
- Projects already invested in standardized RPC frameworks like gRPC, which offer broader ecosystem tools and multi-language compatibility.
Pros & Cons
Pros
Remoc ensures compile-time safety for remote objects and RPC calls, reducing runtime errors in distributed systems as emphasized in its philosophy.
Supports TCP, TLS, WebSockets, and custom transports via a unified interface, allowing adaptation to diverse network environments without lock-in.
Multiple logical streams over a single physical connection reduce overhead, improving performance for concurrent communications in microservices.
With TLS and optional authentication, Remoc provides secure connections out of the box, essential for distributed applications handling sensitive data.
Cons
Automatic serialization and deserialization for remote objects can add latency, making it less ideal for high-frequency, real-time applications where performance is paramount.
Being Rust-focused, Remoc requires additional bridging layers for integration with systems in other languages, unlike frameworks like gRPC that offer native multi-language support.
Configuring remote objects, channels, and RPC involves more initial code compared to simpler socket-based libraries, which can slow down prototyping.
Frequently Asked Questions
Related Projects
HurlHurl, run and test HTTP requests with plain text.
tonicA native gRPC client & server implementation with async/await support.
irohIP addresses break, dial keys instead. A library that adds QUIC + NAT Traversal to your apps.
quiche🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.