NATS
nsq
Our great sponsors
NATS | nsq | |
---|---|---|
11 | 14 | |
5,121 | 24,530 | |
1.6% | 0.5% | |
9.1 | 6.3 | |
about 20 hours ago | 1 day ago | |
Go | Go | |
Apache License 2.0 | MIT License |
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
- High-Performance server for NATS.io, the cloud and edge native messaging system
- Asyncapi with Go
-
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
-
Plugins vs Microservices
You can build monolith applications and if they need cross communication, rely on something like Nats: https://github.com/nats-io/nats.go
- 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
nsq
- NSQ: Open-source realtime distributed messaging, billions of messages / day
-
MQTT vs. Kafka: An IoT Advocate's Perspective
Interesting. What are you thoughts on NSQ?
Was looking at it earlier today, but haven't ever tried it out.
-
Any thoughts on using Redis to extend Go's channels across application / machine boundaries?
(G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it.
-
FileWave: Why we moved from ZeroMQ to NATS
Bit.ly's NSQ is also an excellent message queue option.
-
Infinite loop pattern to poll for a queue in a REST server app
Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers.
- NSQ – A realtime distributed messaging platform
-
What are pros and cons of Go?
distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on)
- Nsq - A realtime distributed messaging platform
- Is there any conventionally accepted repo that is representative of well designed go code ?
- NSQ: A realtime distributed messaging platform
What are some alternatives?
Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
EventBus - [Go] Lightweight eventbus with async compatibility for Go
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
go-nsq - The official Go package for NSQ
Apache Kafka - Mirror of Apache Kafka
dbus - Native Go bindings for D-Bus
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
emitter - Emits events in Go way, with wildcard, predicates, cancellation possibilities and many other good wins
etcd - Distributed reliable key-value store for the most critical data of a distributed system
Confluent Kafka Golang Client - Confluent's Apache Kafka Golang client
consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.