You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a flow adapter for kaffe I use extensively and I'm thinking about open sourcing it. The adapter merges incoming kafka messages to a given Stream.resource/3 that can then be processed, partitioned, windowed, etc. using flow (or other libraries).
My question is this - is this something Kaffe would be interested in having as part of its offering or should I offer it separately. If separate, would you be ok with a name like Kaffe.Stream or would you like something without Kaffe in the name?
The text was updated successfully, but these errors were encountered:
@stevehebert It sounds fairly special purpose, so I don't think it would necessarily fit within Kaffe itself. However, calling it Kaffe.Stream is fine with us!
@stevehebert I'd love to hear more details about how you're using Flow for your Kafka stream processing. I imagine it's very domain specific, but a pseudo-code like overview would be interesting?
I have a flow adapter for kaffe I use extensively and I'm thinking about open sourcing it. The adapter merges incoming kafka messages to a given Stream.resource/3 that can then be processed, partitioned, windowed, etc. using flow (or other libraries).
My question is this - is this something Kaffe would be interested in having as part of its offering or should I offer it separately. If separate, would you be ok with a name like Kaffe.Stream or would you like something without Kaffe in the name?
The text was updated successfully, but these errors were encountered: