go-nsq
The official Go package for NSQ (by nsqio)
mangos
mangos is a pure Golang implementation of nanomsg's "Scalablilty Protocols" (by nanomsg)
go-nsq | mangos | |
---|---|---|
1 | 2 | |
2,536 | 646 | |
0.5% | 1.1% | |
2.1 | 6.2 | |
4 days ago | 12 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
go-nsq
Posts with mentions or reviews of go-nsq.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-19.
-
Distributed IM Service in Golang
nsq : simple, high performance, distributed MQ
mangos
Posts with mentions or reviews of mangos.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-07.
- What would be a good message broker internal to my program?
-
Reconnect to a server
I'm writing a client application that uses https://github.com/nanomsg/mangos to connect to a server using the PUB/SUB protocol. I'm not sure how to handle server or network interrupts on the client. The application is just a for loop waiting for a message to arrive and the call a go routine to handle that message. Does anybody know a good example how to deal with network or server failures in GO? Or should the application just panic and let the OS create a new instance of the application? The client application will run as a daemon so users can not interact with it.
What are some alternatives?
When comparing go-nsq and mangos you can also consider the following projects:
NATS - Golang client for NATS, the cloud native messaging system.
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
dbus - Native Go bindings for D-Bus
Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.
pubsub - A simple pubsub package for go.
zmq4 - A Go interface to ZeroMQ version 4
Asynq - Simple, reliable, and efficient distributed task queue in Go
messagebus - Go simple async message bus
Benthos - Fancy stream processing made operationally mundane
EventBus - [Go] Lightweight eventbus with async compatibility for Go