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.
We're looking to replace the http broker with an embedded NATS broker. NATS is a phenomenal messaging system which we've been using since 2016 and find that as we're moving towards grpc for the client/server we want something equally powerful for messaging.
Considering NATS will bake in persistence with jetstream soon this feels like a good fit.
How it works. With no arguments specified, services will start the embedded nats broker on random ports, one for the client and the other for internal clustering. The internal client will connect to the client port and other servers will find the server via the registry and cluster with it.
We're not yet rereading for changes in the registry because nats servers gossip and should be able to account for the changes.