Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Embedded NATS Broker #1110

Merged
merged 5 commits into from Jan 14, 2020
Merged

Embedded NATS Broker #1110

merged 5 commits into from Jan 14, 2020

Conversation

asim
Copy link
Member

@asim asim commented Jan 14, 2020

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.

@asim asim merged commit 1d311ab into master Jan 14, 2020
@asim asim deleted the embedded-nats branch January 14, 2020 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant