[PoC] Adding Kafka as Event Publishing Alternative to Rabbit #791
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related #465
Added an integration with Kafka using the
Confluent.Kafka
package.I heavily followed the patterns established from the RabbitMq integration. At the moment, my testing has been limited to the integration testing that is included with this PR.
I would love to get some feedback, and discuss any changes that would need to be made in order for this integration to move forward.
Notes
IEventFlowOptions
builder:Func<IDomainEvent, TopicPartition> topicPartitionFactory
Edit: Looks like the integration test is timing out, unfortunately a Kafka broker doesn't expose any kind of meaningful health check, at least not without adding a third container for diagnostics. I can try to crank up the timeout in the integration test, but I would rather not burn through your CI time if there are more structural concerns with this change to address first.