I also found it hard to discern the architecture There are storage backends, there is a router component... the examples at http://zenoh.io/docs/getting-start

I also found it hard to discern the architecture There are storage backends, there is a router component... the examples at http://zenoh.io/docs/getting-started/first-app/ http://zenoh.io/docs/getting-started/first-app/ show curl-ing to the router(?), and it's presumably the router that talks to storage backend... so Zenoh is the router, and that runs on the remote device? https://github.com/eclipse-zenoh/zenoh-python/tree/master/examples/zenoh-net https://github.com/eclipse-zenoh/zenoh-python/tree/master/ex... Alternative to the REST API it appears there is also some sort of peer network, and it mentions Zenoh peers and routers as separate entities? The docs would benefit from some diagrams and definition of terms