ZeroMQ VS Resque

In this post from 2011, the creator of Omegle, Leif Brooks, explains what technology is used, including Python and a library called gevent for the backend. On top of that, Adobe Cirrus is used for streaming video. Though this post was 12 years ago, it is valuable to know what a web application like Omegle requires. A modern library that may provide some functionality for a text chat at a minimum may be... Source: 6 months ago

They might be thinking of something like ZeroMQ, which is pretty well liked: https://zeromq.org/ That said, I wouldn't call RabbitMQ that heavyweight myself, at least when compared to something like Apache Kafka. - Source: Hacker News / 7 months ago

If you want to learn message passing in an environment you're familiar with, you should check out ZeroMQ. It's a C++ lib for socket abstraction, it's immensely useful in distributed systems, it can also do in-process message passing, and it's got bindings/ports for C and Rust. Source: 12 months ago

Inspired by the IDE language server protocol, I created an API interface between the electron and the Python ML interface. ZeroMQ turned out be an invaluable resource as a fast and lightweight messaging queue between the two. - Source: dev.to / about 1 year ago

If you really need it live, like for a chat or auctions you can use https://zeromq.org/ over websockets. Source: about 1 year ago

You can use a background job queue like Resque to scrape and process data in the background, and a scheduler like resque-scheduler to schedule jobs to run your scraper periodically. Source: almost 2 years ago

So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago

Background jobs are another limitation. Since only the Aha! Web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck. - Source: dev.to / about 2 years ago

The Schedules worker corresponds to the appwrite-schedule service in the docker-compose file. The Schedules worker uses a Resque Scheduler under the hood and handles the scheduling of CRON jobs across Appwrite. This includes CRON jobs from the Tasks API, Webhooks API, and the functions API. - Source: dev.to / about 3 years ago

There are a few of popular systems. A few need a database, such as Delayed::Job, while others prefer Redis, such as Resque and Sidekiq. - Source: dev.to / about 3 years ago