NATS VS mangos

Compare NATS vs mangos and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
NATS mangos
11 2
5,136 645
2.0% 2.2%
9.1 6.3
about 16 hours ago 4 days ago
Go Go
Apache License 2.0 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.

NATS

Posts with mentions or reviews of NATS. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-21.

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?
    3 projects | /r/golang | 7 Sep 2022
  • Reconnect to a server
    3 projects | /r/golang | 3 Mar 2021
    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 NATS and mangos you can also consider the following projects:

nsq - A realtime distributed messaging platform

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.

EventBus - [Go] Lightweight eventbus with async compatibility for Go

go-nsq - The official Go package for NSQ

zmq4 - A Go interface to ZeroMQ version 4

messagebus - Go simple async message bus

emitter - Emits events in Go way, with wildcard, predicates, cancellation possibilities and many other good wins