Change queue model to pub-sub model#57
Merged
vongosling merged 10 commits intoopenmessaging:topic_modelfrom Nov 22, 2019
Merged
Change queue model to pub-sub model#57vongosling merged 10 commits intoopenmessaging:topic_modelfrom
vongosling merged 10 commits intoopenmessaging:topic_modelfrom
Conversation
duhenglucky
changed the title
vongosling
approved these changes
Nov 14, 2019
litianyu1992
approved these changes
Nov 14, 2019
Collaborator
|
Agree, I think the pub/sub model would be easy to understand and embraced warm-hearted by many exist messaging solutions. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As the current mainstream messaging middleware uses a topic-based pub-sub model, the proposal hopes to change the OpenMessaging queue based model to a pub-sub based model, which will bring some benefits:
(1) Mainstream messaging middleware is easier to adapt
(2) Users can accept OpenMessaging more naturally
(3) API can be more streamlined, providing a more abstract specification interface