-
Notifications
You must be signed in to change notification settings - Fork 30
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
Feature request: golang nats driver #549
Comments
Hello! From what I understand, NATS is a message broker. Even if this project uses it as a pub/sub driver, how would it make rolling out easier? Are there any issues with using Redis as the backend for data storage and publishing/subscribing to events? |
nats server can be embedded. Or it can be run stand alone . its 109% golang . its much easier to run then Redis , faster and has security and lots more . so its very easy to rollout , and yes its a message broker. I have seen benchmarks of it against Redis and it’s twice as fast . I typically put 3 nats in each main data center . Then clients automagically connect to the nearest data center . I am def a fan boy though :) |
https://github.com/RussellLuo/hats It’s a nats web hook system |
I understand, thank you! But you still need Redis to share the data among the app replicas, right? |
Nats does that just fine . you probably need to look at nats examples … |
Would you open to adding nats as a driver in https://github.com/tarampampam/webhook-tester/tree/master/internal/pubsub
there is an example here :
https://github.com/RussellLuo/hats
Nats server is golang and can be globally cluster and so in some ways is much easier to roll out .
If you want to have no runtime dependencies you can run nats embedded as a leaf .
If , but unlikely, you want to run inprocess, but can be embedded and started that way too.
Feel free to ask if your not so familiar with nats.
The text was updated successfully, but these errors were encountered: