In Dataflow, we currently have support for Kafka, Jetstream, NATS Streaming and other sources and sinks. It would be amazing to add support for NSQ too. We know that we plenty of use cases in the OSS community and this would get a lot of love.
The Dataflow team are not NSQ experts. My ask is - would anyone be interested in implementing the changes needed?
Here is a pull request for Jetstream, breaking it down:
- Add manifests to install a dev NSQ into Kubernetes cluster.
- Add APIs to specify a NSQ source and sink (e.g. the URL, authentication).
- Implement the source and sink.
- Write test infrastructure (e.g. check the right number of messages get written to a sink).
- Write tests (e.g. does the right number of message get written, even if the pod is deleted).
- Write examples.
- Write docs.
I'll raise a ticket against the main repo, and the Go client repo (there might be engineers there with the exact skills needed).
In Dataflow, we currently have support for Kafka, Jetstream, NATS Streaming and other sources and sinks. It would be amazing to add support for NSQ too. We know that we plenty of use cases in the OSS community and this would get a lot of love.
The Dataflow team are not NSQ experts. My ask is - would anyone be interested in implementing the changes needed?
Here is a pull request for Jetstream, breaking it down:
I'll raise a ticket against the main repo, and the Go client repo (there might be engineers there with the exact skills needed).