sidekiq.cr
nsq
Our great sponsors
| sidekiq.cr | nsq | |
|---|---|---|
| 1 | 14 | |
| 764 | 24,516 | |
| - | 0.4% | |
| 2.9 | 6.3 | |
| 12 months ago | 11 days ago | |
| Crystal | Go | |
| GNU Lesser General Public License v3.0 only | 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.
sidekiq.cr
-
New Gem for background job processing from Ruby/Rails -> Crystal
FWIW you can just write Sidekiq workers in Crystal (although I don't think it supports pro feature.
nsq
-
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.
-
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)
- Is there any conventionally accepted repo that is representative of well designed go code ?
-
Distributed IM Service in Golang
NSQ is a message queue implemented by Golang, and all messages are routed through NSQ. Reasons for choosing NSQ compared to other MQs: decentralized distribution (direct connection between production and consumption), low latency, No ordering, high performance, simple binary protocol.
-
Fluvio: The Programmable Data Platform
If we are talking about "cloud-native", I would really recommend taking a look at nsq or nats. I am really big fanboy of NSQ [1], it is simple, easy to setup and conceptually easy to learn.
[1] https://nsq.io
-
For those running Go in production at scale, what do you use for distributed task queues?
Here is link number 1 - Previous text "NSQ"
I've been using NSQ in production for a number of years now. It's also written in Go and has a first class client library maintained by the devs
What are some alternatives?
NATS - Golang client for NATS, the cloud native messaging system.
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
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
crystal-resque-client - :ambulance: Simple Resque queue client for Crystal
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.
Asynq - Simple, reliable, and efficient distributed task queue in Go
BeanstalkD - Beanstalk is a simple, fast work queue.