feat: Kafka protocol example #625
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Femi <alayesanmifemi@gmail.com>
Signed-off-by: Femi <alayesanmifemi@gmail.com>
Signed-off-by: Femi <alayesanmifemi@gmail.com>
Signed-off-by: Femi <alayesanmifemi@gmail.com>
Signed-off-by: Femi <alayesanmifemi@gmail.com>
|
It might be beneficial for others if there was a readme that shows how to use the example as well as showing how to setup a local kafka instance |
…usage Signed-off-by: Femi <alayesanmifemi@gmail.com>
Absolutely! Thanks for the feedback, I added a readme and docker compose file for this @lholmquist |
|
@FemiOfficial thanks for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed Changes
Added an end to end example for kafka message protocol.
Description
It is a simple cli application where from a user input, the kafka producer sends a CloudEvent message to a topic. And eventually, the cloudevent message is handled and deserialized correctly by a consumer subscribed to the same topic.
Message sent from the Producer (CLI Input)
Message received and deserialised by the Consumer
Fixes this Issue
#463