Fork me on GitHub
#onyx
<
2018-05-14
>
Drew Verlee01:05:44

How do pyrostore and onyx relate?

lucasbradstreet01:05:05

The archiver component is built with Onyx, but does not expose anything about Onyx to users. The consumer does not use onyx at all, since the data is in the right layout at that point. onyx-kafka can be easily configured to consume from Pyrostore (blended with real-time kafka data when required).

lucasbradstreet01:05:36

It’s mostly a second product from Distributed Masonry, with some user overlap.

Drew Verlee01:05:16

gotcha! That makes sense to me.

mccraigmccraig11:05:36

@lucasbradstreet i'm interested in pyrostore - should i go through the webform for more info ?

joelsanchez20:05:35

I have an input task and a function task, and I want to execute an input task based on the output - is this impossible? how can workflows be composed?

lucasbradstreet21:05:18

You’re best off chaining the two jobs using storage of some kind. e.g. output to kafka, have another job read from kafka

👍 4