nsq-event-bus
NATS
Our great sponsors
nsq-event-bus | NATS | |
---|---|---|
0 | 11 | |
77 | 5,097 | |
- | 2.3% | |
0.0 | 9.1 | |
about 6 years ago | 4 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nsq-event-bus
We haven't tracked posts mentioning nsq-event-bus yet.
Tracking mentions began in Dec 2020.
NATS
-
High-Performance server for NATS.io, the cloud and edge native messaging system
(note that NATS Streaming is a now deprecated predecessor to NATS JetStream)
Pull does have advantages over push (e.g. one-to-one flow control since the transfer of the messages is initiated by the client (pull requests)), and they are basically functionally equivalent (only thing push can do that pull can not is send a copy of all the message to all the subscribers, should you ever need it). They both exists because historically push came first and then pull later).
As a developper using NATS JetStream you should really not have to worry about push or pull, you should just care whether you want to consume the messages via call back or via an iterator or via fetching batches, after that whether pull or push is being used underneath the covers is irrelevant to you.
And this is exactly how it is in the new JetStream API (https://github.com/nats-io/nats.go/tree/main/jetstream#readm...) you don't have to worry about push/pull anymore and you can consume in any of the 3 ways described above (callback, iterator, fetch batch) it's all a lot simpler and easier to use.
-
What is the coolest Go open source projects you have seen?
nats: Golang client for NATS, the cloud native messaging system
-
Distributed communication patterns with NATS
Install the nats.go package
- Redis vs. Kafka vs. RabbitMQ
-
Distributed messaging with NATS
Now that our NATS server is running, we'll be using Go and Node.js clients to connect to it for simple demonstration. Not familiar with Go or Node? Don't worry NATS has clients available in over 40 languages!
- How do I build a text editor like notepad using wails
- Modern Communication: Sockets
-
Subscription management in pub/sub system
You could start by looking/reading how it is implemented in production ala https://github.com/nats-io/nats.go
What are some alternatives?
nsq - A realtime distributed messaging platform
Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.
EventBus - [Go] Lightweight eventbus with async compatibility for Go
go-nsq - The official Go package for NSQ
dbus - Native Go bindings for D-Bus
emitter - Emits events in Go way, with wildcard, predicates, cancellation possibilities and many other good wins
Confluent Kafka Golang Client - Confluent's Apache Kafka Golang client
mangos - mangos is a pure Golang implementation of nanomsg's "Scalablilty Protocols"
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
zmq4 - A Go interface to ZeroMQ version 4
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
pubsub - A simple pubsub package for go.