A lightweight library that adds job scheduling capabilities to RQ (Redis Queue) (by rq)


Basic rq-scheduler repo stats
9 days ago

rq/rq-scheduler is an open source project licensed under MIT License which is an OSI approved license.

Rq-scheduler Alternatives

Similar projects and alternatives to rq-scheduler based on common topics and language

  • GitHub repo supervisor

    Supervisor process control system for UNIX

  • GitHub repo redis-sitesearch

  • GitHub repo Flask-RQ2

    A Flask extension for RQ.

  • GitHub repo rq

    Simple job queues for Python

  • GitHub repo django-rq

    A simple app that provides django integration for RQ (Redis Queue)

  • GitHub repo celery

    Distributed Task Queue (development branch)

  • GitHub repo dramatiq

    A fast and reliable background task processing library for Python 3.

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better rq-scheduler alternative or higher similarity.


Posts where rq-scheduler has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-02-08.
  • Need direction on how to add asynchronous / scheduled tasks on my flask app running on aws beanstalk
    reddit.com/r/flask | 2021-03-14
  • Some advice: will my setup be production ready?
    reddit.com/r/django | 2021-02-08
    Some thoughts: - Storing API keys in Redis with AOF and RDB persistence turned on is going to be way faster than storing those keys in Mongo. - Did you mean RQ (redis-queue)/django-rq? If so, it works well as long as you don't need a scheduler for cron-like tasks, which it doesn't include. You can add rq-scheduler for that though: https://github.com/rq/rq-scheduler - Make sure your redis instance has a password -- redis 6 supports ACLs as well - The problem with slow requests is that they tie up app server processes and usually also database connections. That may be fine with a small number of consumers, but if you point your web site at this API, you may run into problems. Consider that if an app server serving web site traffic is waiting for a slow request to your API, then both app servers are affected -- you're now holding resources on the web site and the API, effectively. - HTTP clients often use a default timeout value for requests, and it's a best practice to use such a timeout -- so you'll need to coach your partners consuming this API not to use timeouts for your API.