3. currently, there's no adhoc way to query in-memory data. wallaroo while having a couple database like features isn't a database. you'd need to export that ag

3. currently, there's no adhoc way to query in-memory data. wallaroo while having a couple database like features isn't a database. you'd need to export that aggregation or the results thereof via a sink into some other system for adhoc querying. we've had discussions about providing adhoc querying but it isn't on the immediate radar. 4. we've worked with folks who want to do what you are describing but the "answer channel" was different than the "question channel". so the question came in over a source (in their case TCP) and the answer would leave over a sink (also TCP). in that case it was something like: client -> persistent web socket -> server -> streaming system -> server -> persistent web socket -> client having a combined source/sink is something that we've discussed but we have higher priorities at the moment. if we were to start working with someone for whom it was a priority, we'd move it up in priority.