zmq4
A Go interface to ZeroMQ version 4 (by pebbe)
mangos
mangos is a pure Golang implementation of nanomsg's "Scalablilty Protocols" (by nanomsg)
Our great sponsors
| zmq4 | mangos | |
|---|---|---|
| 1 | 2 | |
| 1,135 | 645 | |
| - | 2.2% | |
| 3.6 | 6.3 | |
| about 1 month ago | 6 days ago | |
| Go | Go | |
| BSD 2-clause "Simplified" 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.
zmq4
Posts with mentions or reviews of zmq4.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-06.
-
How to use ZeroMQ Request-Reply Pattern in Golang
The framework I'm going to use is fiber and the ZeroMQ client that I'm going to use is zmq4.
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 zmq4 and mangos you can also consider the following projects:
dbus - Native Go bindings for D-Bus
NATS - Golang client for NATS, the cloud native messaging system.
Uniqush-Push - Uniqush is a free and open source software system which provides a unified push service for server side notification to apps on mobile devices.
pubsub - A simple pubsub package for go.
Benthos - Fancy stream processing made operationally mundane
go-nsq - The official Go package for NSQ
messagebus - Go simple async message bus
go-mq - Declare AMQP entities like queues, producers, and consumers in a declarative way. Can be used to work with RabbitMQ.
EventBus - [Go] Lightweight eventbus with async compatibility for Go