work
nsq
| work | nsq | |
|---|---|---|
| 5 | 14 | |
| 2,318 | 24,589 | |
| 0.6% | 0.3% | |
| 0.0 | 6.1 | |
| about 1 month ago | 3 days ago | |
| Go | Go | |
| MIT License | 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.
work
- Looking for library recommendations: Django -> Golang port
-
5 Tips to help your App scale
What to check out: AWS SQS, Cloud Tasks, render.com background workers, Heroku workers, Go Worker
-
For those running Go in production at scale, what do you use for distributed task queues?
One of the gocraft/work maintainers here. Gocraft/work is not abandoned; we are just thinking what v2 could become, and working on v2: https://github.com/gocraft/work/issues/120#issuecomment-530615442
-
Best alternative at the Sidekiq at Go?
We’ve been using this one in production https://github.com/gocraft/work
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?
Asynq - Simple, reliable, and efficient distributed task queue in Go
NATS - Golang client for NATS, the cloud native messaging system.
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
gocelery - Celery Distributed Task Queue in Go
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
cadence - Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
Apache Kafka - Mirror of Apache Kafka
temporal - Temporal service
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
rabbit-hole - RabbitMQ HTTP API client in Go
etcd - Distributed reliable key-value store for the most critical data of a distributed system