Yes, already thinking about what will come shortly after Version 6 is released.
Under consideration:
Maybe evaluate System.Text.Json to replace the dependency on Newtonsoft.
I could help with Kafka, I used to use it often
Hi,
Just to clarify, I understand that the support would be for messages coming from Kafka/Event Hubs.
If I look at current implementation, I can see that answering to the same transport should be supported (?).
Is the support for "publishing only" use cases included in the vision for this 6.1 version?
I'm not sure what you mean by publishing only, but I do plan to make it so that the message serialization is easily used from other sources (probably Java and Python) to send messages in the proper envelope.
Sorry for being unclear, and thanks for your answer.
I am very probably mistaken, but I understood from the documentation that you could publish a message on Kafka after receiving one from Kafka (consumer that will use the context to publish on the same bus), but did not see anything about publishing a message to Kafka directly.
Will this be a supported scenario?
I'm not sure yet - but more than likely this would include Publish support (and probably Send as well). The only real difference would be things like _not_ moving messages to _error or _skipped queues since it's a log already, it would just publish a Fault and MoveOn.
Would love to see a Google Pub/Sub transport being considered!
Kafka support sounds awesome!
Most helpful comment
Kafka support sounds awesome!