Max Meldrum

So if I understood the outcome of the discussion it was that we compile the same binary (see below). But through the control plane glue different stages of the pipeline...

I don't fully understand the non-deterministic part. When are users gonna create different dataflows based on input parameter? Then can't we assume that the input parameter would be same for...

> > So if I understood the outcome of the discussion it was that we compile the same binary (see below). But through the control plane glue different stages of...

> The user machine could run the driver and the others could run the network managers. Do you think this could be of help or is it not so useful?...

## Tokio The other approach is to adopt tokio and use a similar approach to the actix [runtime](https://github.com/actix/actix-net/blob/master/actix-rt/src/runtime.rswhe) where they spawn a runtime per thread and combine it with a...

> I wonder if we could combine kompact and tokio to get "the best of both worlds". Tokio integrates us with the async ecosystem which I think is crucial for...

I'm very interested in this feature. Currently using it on a fork together with #529. Would love to help get it merged if there is something left remaining. Also, wondering...

It is also pulling in a bunch of other crates by default. Possible fix: ```toml [features] default = ["persistent"] # or any other suitable name (rocksdb) persistent = [ "dep:rocksdb",...

> I wondered if it works with the distributed warehouse? I would say that µWheel can be used in two different modes: **Stream Mode:** This mode assumes that the wheel...

An early prototype of a ``WheelManager``can be seen here: https://github.com/Max-Meldrum/wheel_manager/blob/main/examples/nyc_taxi.rs It manages wheels over a set of parquet files. Right now, it only builds a ``COUNT``wheel for the table and...