Powerful SaaS integration toolkit for SaaS developers - create, amplify, manage and publish native integrations from within your app with Cyclr's flexible Embedded iPaaS.
featured
Dramatiq
Sidekiq
RabbitMQ
Apache Kafka
NoobHub
delayed_job
ZeroMQ
Resque
NSQ
ZeroMQ
RabbitMQ
nanomsg
Apache Kafka
Apache ActiveMQ
ubus
D-Bus
DramatiqDramatiq might be a bit more popular than NSQ. We know about 8 links to it since March 2021 and only 7 links to NSQ. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Using something like Dramatiq [1] with Redis, writing a background job takes minutes, and can be deployed alongside an existing Python web app. There are probably JS equivalents. I think Inngest could be a useful service, but the comparison felt off for me - it made me feel like this wasn't solving a real problem. [1] https://dramatiq.io/. - Source: Hacker News / 10 months ago
Hello everyone. We want to present you Taskiq: our new project that allows sending tasks using distributed queues. Conceptually it's similar to Celery or Dramatiq but with full asyncio and type hints support. Taskiq can send and execute async functions and has many integrations with different queue implementations. Source: about 1 year ago
I spent 3 years building a high scale crawler on top of Celery. I can't recommend it. We found many bugs in the more advanced features of Celery (like Canvas) we also ran into some really weird issues like tasks getting duplicated for no reason [1]. The most concerning problem is that the project was abandoned. The original creator is not working on it anymore and all issues that we raised were ignored. We had to... - Source: Hacker News / over 1 year ago
I have been using dramatiq lately (celery alternative) and so far I'm happy with it. Source: almost 2 years ago
If your tasks are idempotent, Dramatiq if intended for your case. https://dramatiq.io/. - Source: Hacker News / almost 2 years ago
(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. Source: about 1 year ago
Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago
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. Source: over 1 year ago
Distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on). Source: almost 2 years ago
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. - Source: dev.to / about 2 years ago
Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby
ZeroMQ - ZeroMQ is a high-performance asynchronous messaging library.
RabbitMQ - RabbitMQ is an open source message broker software.
Apache Kafka - Apache Kafka is an open-source message broker project developed by the Apache Software Foundation written in Scala.
nanomsg - nanomsg is a socket library that provides several common communication patterns.
NoobHub - OpenSource multiplayer and network messaging.