Add RabbitConnection for RabbitMQ #12
Merged
Conversation
This file contains 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
Kafka needs topics to exist before startup, RabbitMQ can only initialize the channels after startup.
Avoid dynamically creating/destroying clients and topics on every RPC request
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.
Add support for RabbitMQ, cause we are fed up with how complex Kafka is to maintain.
While RabbitMQ allows dynamically creating and removing topics (since technically it doesn't even work on "topics", it uses queues, exchanges and routing keys), to avoid doing so on every RPC request, the RPC client has been updated to always keep the response producer/consumer around.