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

Rq-scheduler Alternatives

Similar projects and alternatives to rq-scheduler

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

rq-scheduler reviews and mentions

Posts with mentions or reviews of rq-scheduler. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-24.
  • Keep the Monolith, but Split the Workloads
    8 projects | news.ycombinator.com | 24 Apr 2023
  • RQ-Scheduler for tasks in far future?
    2 projects | /r/Python | 28 Dec 2022
    RQ-Scheduler is another simpler alternative (rq/rq-scheduler: A lightweight library that adds job scheduling capabilities to RQ (Redis Queue) (github.com)) that appears to be good for such purposes. It's not immediately clear if it would suffer from the same issues, but it seems not (Redis manages issues with data loss well, a separate queue is used for the scheduled tasks, etc.). Is anyone aware of any drawbacks to using RQ-Scheduler for something like this?
  • Some advice: will my setup be production ready?
    3 projects | /r/django | 8 Feb 2021
    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.
  • A note from our sponsor - WorkOS
    workos.com | 1 Mar 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →


Basic rq-scheduler repo stats
about 2 months ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives