A zero-overhead protocol that unifies data in motion, at rest, and computations via pub/sub, geo-distributed storage, and queries.
Eclipse Zenoh is a unified protocol that combines data in motion (pub/sub), data at rest (storage), and computations into a single, efficient stack. It solves the problem of fragmented data handling in distributed systems by providing geo-distributed storage, queries, and real-time messaging with minimal overhead.
Developers and architects building high-performance distributed systems, IoT applications, edge computing solutions, and real-time data pipelines that require unified data access and low-latency communication.
Developers choose Zenoh for its exceptional efficiency (zero overhead), ability to unify multiple data paradigms (pub/sub, storage, queries), and support for geo-distributed deployments, eliminating the need for multiple disparate technologies.
zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The README highlights efficient real-time data distribution with minimal latency and resource usage, as demonstrated in the z_pub and z_sub examples that showcase low overhead communication.
Zenoh seamlessly blends pub/sub, geo-distributed storage, and computations into a single stack, eliminating the need for multiple disparate technologies and reducing system complexity.
It enables direct querying of data from storages or computations via the network, providing flexible data access as shown in the z_queryable and z_get examples for dynamic data retrieval.
With libraries available in Rust, C, C++, Python, Java, Kotlin, and TypeScript, Zenoh offers broad language interoperability, though most bindings rely on the core Rust implementation.
Building Zenoh requires the Rust toolchain and careful handling of features, with dependencies that may need newer Rust versions, adding setup overhead and potential compatibility issues.
The plugin architecture is extensible, but the ecosystem is smaller compared to established solutions, with plugins developed separately and community support primarily through Discord, hindering rapid adoption.
Internal crates in 'commons' can change at any time, and only 'zenoh' and 'zenoh-ext' have stable APIs, posing a risk for projects that might inadvertently rely on unstable components.