hydroflow 0.10.0

Hydro's low-level dataflow runtime and IR
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39

A less simple version of the `kvs` example, with multi-node replication. Each server can connect to
an existing peer server, and updates will be gossiped between them.

Current semantics are:
 - PUTs are appended: we remember them all forever
 - GETs are only remembered for the current tick, which may not be monotone depending on how they
   are consumed.
 - GETs for empty keys get no acknowledgement.

 Clients accept commands on stdin. Command syntax is as follows:
 - `PUT <key>, <value>`
 - `GET <key>`
 Commands are case-insensitive. All keys and values are treated as `String`s.

## Running the example

We will need four (or more) terminals:

First, start a server:
```
cargo run -p hydroflow --example kvs_replicated -- --role server --addr localhost:12346
```

In another terminal connect a client to the first server:
```
cargo run -p hydroflow --example kvs_replicated -- --role client --addr localhost:9090 --server-addr localhost:12346
```

Then, run a second server to connect to to the first server:
```
cargo run -p hydroflow --example kvs_replicated -- --role server --addr localhost:12347 --server-addr localhost:12346
```

And finally we can run a second client to connect to the second server:
```
cargo run -p hydroflow --example kvs_replicated -- --role client --addr localhost:9091 --server-addr localhost:12347
```

Adding the `--graph <graph_type>` flag to the end of the command lines above will print out a node-and-edge diagram of the program. Supported values for `<graph_type>` include [mermaid](https://mermaid-js.github.io/) and [dot](https://graphviz.org/doc/info/lang.html).