NOISSUE - Use NATS as MQTT broker #2681
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
rodneyosodo
force-pushed
the
replace-vernemq
branch
from
e2c4528 to
d642abd
Compare
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
rodneyosodo
force-pushed
the
replace-vernemq
branch
from
9b44227 to
334ac2a
Compare
dborovcanin
approved these changes
Feb 3, 2025
dborovcanin
changed the title
rodneyosodo
added a commit
to rodneyosodo/supermq
that referenced
this pull request
Feb 7, 2025
This reverts commit cff6e7f.
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.
What type of PR is this?
This is a refactor because it removes removes VerneMQ as the MQTT broker and use NATS instead.
What does this do?
Enhancements:
Tests:
Which issue(s) does this PR fix/relate to?
Related to #2021
Have you included tests for your changes?
Yes, I have included tests for my changes.
Did you document any new/modified feature?
Yes, I have updated the documentation for the new feature.
Notes
Sequence Diagram(s)
sequenceDiagram participant C as Client participant A as MQTT Adapter participant N as NATS Broker C->>A: Publish MQTT Message A->>N: Forward message (no MQTT tracing/forwarder) N-->>A: Acknowledge receipt A-->>C: Confirm delivery