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

Replace nanomsg with a proper message queue #56

Open
0xB10C opened this issue Oct 22, 2024 · 2 comments · May be fixed by #76
Open

Replace nanomsg with a proper message queue #56

0xB10C opened this issue Oct 22, 2024 · 2 comments · May be fixed by #76

Comments

@0xB10C
Copy link
Owner

0xB10C commented Oct 22, 2024

Nanomsg is currently used by the extractor to publish messages to tools who subscribe to a TCP socket. Nanomsg has a few downsides:

  • Only one publisher can exist, we might want to have multiple (a tracing publisher, and a RPC publisher, possibly a ZMQ publisher, ...)
  • The nanomsg crate isn't maintained. The last update was 6 years ago..
  • We can't easily record and play back messages, other message queues with brokers allow this
@0xB10C
Copy link
Owner Author

0xB10C commented Oct 22, 2024

One solution could be NATS. It allows for:

@0xB10C 0xB10C linked a pull request Nov 9, 2024 that will close this issue
@i-am-yuvi
Copy link
Collaborator

Interesting!! Let's see how this behaves with other tools!!

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 a pull request may close this issue.

2 participants