A declarative data-flow programming framework built on Zenoh for building applications that span from cloud to edge devices.
Zenoh-Flow is a declarative data-flow programming framework built on the Zenoh communication middleware. It simplifies the creation, deployment, and management of complex distributed applications that operate across cloud and edge environments by structuring computations as directed graphs of computing units.
Developers and engineers building distributed systems, IoT applications, or edge computing solutions that require seamless communication and computation across cloud and device layers.
It uniquely combines the structural clarity of data-flow programming with Zenoh's location-transparent communication, allowing developers to focus on application logic without managing infrastructure complexities, making it ideal for scalable cloud-to-edge deployments.
zenoh-flow aims at providing a zenoh-based data-flow programming framework for computations that span from the cloud to the device.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables structuring applications as directed graphs of computing units, simplifying complex distributed computations, as highlighted in the key features for declarative data-flow programming.
Leverages Zenoh's middleware to automatically handle data publication and subscription without manual location management, enabling seamless operation across cloud and edge environments.
Abstracts away underlying infrastructure complexities, allowing developers to focus on application logic rather than deployment details, as emphasized in the philosophy.
Designed to support applications operating from cloud to edge devices ('things'), providing built-in flexibility for heterogeneous deployments, as stated in the description.
Requires understanding both data-flow programming concepts and the Zenoh middleware, which can be challenging for developers new to distributed systems or this stack.
Documentation is maintained in a Wiki, which may be less structured or incomplete compared to integrated docs, as noted in the README with links to external resources.
Deep integration with Zenoh means applications are tightly coupled to this middleware, limiting flexibility if switching to other communication systems is needed.
The abstraction layers and middleware communication introduce latency and resource usage that might not suit high-performance, latency-sensitive applications.