Op-Rabbit
nsq
Our great sponsors
| Op-Rabbit | nsq | |
|---|---|---|
| - | 14 | |
| 234 | 24,561 | |
| 0.0% | 0.6% | |
| 0.0 | 6.3 | |
| over 2 years ago | about 20 hours ago | |
| Scala | Go | |
| GNU General Public License v3.0 or later | 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.
Op-Rabbit
We haven't tracked posts mentioning Op-Rabbit yet.
Tracking mentions began in Dec 2020.
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?
https://github.com/nsqio/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?
elasticmq - In-memory message queue with an Amazon SQS-compatible interface. Runs stand-alone or embedded.
NATS - Golang client for NATS, the cloud native messaging system.
Apache Pulsar - Apache Pulsar - distributed pub-sub messaging system
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
Apache RocketMQ - Apache RocketMQ is a cloud native messaging and streaming platform, making it simple to build event-driven applications.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Apache Kafka - Mirror of Apache Kafka
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
etcd - Distributed reliable key-value store for the most critical data of a distributed system
consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
fluvio - Lean and mean distributed stream processing system written in rust and web assembly.
go-proxy-cache - Simple Reverse Proxy with Caching, written in Go, using Redis.