> zenoh /zeno/ 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.

I wonder what goes into the minds of developers when they use grandiose, unbacked descriptions like this. It is just missing the word "modern" :-)

Wouldn't it be better to have some numbers to compare to those others "mainstream stacks"? It would help to show not only how "fast" zenoh is but also actually what is it (still not sure ...), by comparing to other established players.

Having read http://zenoh.io/docs/overview/#unified-abstractions and being pretty familiar with the IoT space, I also don't yet understand what it's for or why you'd use it instead of X, Y, and/or Z. (I'd like to, though!)

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/ 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/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