J4j4mie·Jan 11, 2023
https://github.com/dabapps/django-db-queue
(I am the author)
EDIT: oh hi, Andy :)
In Django Styleguidedabapps
django-db-queue
Python2022–2023
dabapps / django-db-queue
django-db-queue
Simple database-backed job queue
3Distinct people
3Mentions
0Explicit recommenders
186GitHub stars
What to know before exploring
What it is
Simple database-backed job queue
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:24:10 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week3 dated mentions
Observed mentions: 2022-08-23 12:00:56 UTC to 2023-01-11 14:46:58 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 22 | 2022-08-22 00:00:00 UTC | 2022-08-29 00:00:00 UTC | 1 | 0 | 1 |
| Aug 29 | 2022-08-29 00:00:00 UTC | 2022-09-05 00:00:00 UTC | 0 | 0 | 0 |
| Sep 5 | 2022-09-05 00:00:00 UTC | 2022-09-12 00:00:00 UTC | 1 | 0 | 1 |
| Sep 12 | 2022-09-12 00:00:00 UTC | 2022-09-19 00:00:00 UTC | 0 | 0 | 0 |
| Sep 19 | 2022-09-19 00:00:00 UTC | 2022-09-26 00:00:00 UTC | 0 | 0 | 0 |
| Sep 26 | 2022-09-26 00:00:00 UTC | 2022-10-03 00:00:00 UTC | 0 | 0 | 0 |
| Oct 3 | 2022-10-03 00:00:00 UTC | 2022-10-10 00:00:00 UTC | 0 | 0 | 0 |
| Oct 10 | 2022-10-10 00:00:00 UTC | 2022-10-17 00:00:00 UTC | 0 | 0 | 0 |
| Oct 17 | 2022-10-17 00:00:00 UTC | 2022-10-24 00:00:00 UTC | 0 | 0 | 0 |
| Oct 24 | 2022-10-24 00:00:00 UTC | 2022-10-31 00:00:00 UTC | 0 | 0 | 0 |
| Oct 31 | 2022-10-31 00:00:00 UTC | 2022-11-07 00:00:00 UTC | 0 | 0 | 0 |
| Nov 7 | 2022-11-07 00:00:00 UTC | 2022-11-14 00:00:00 UTC | 0 | 0 | 0 |
| Nov 14 | 2022-11-14 00:00:00 UTC | 2022-11-21 00:00:00 UTC | 0 | 0 | 0 |
| Nov 21 | 2022-11-21 00:00:00 UTC | 2022-11-28 00:00:00 UTC | 0 | 0 | 0 |
| Nov 28 | 2022-11-28 00:00:00 UTC | 2022-12-05 00:00:00 UTC | 0 | 0 | 0 |
| Dec 5 | 2022-12-05 00:00:00 UTC | 2022-12-12 00:00:00 UTC | 0 | 0 | 0 |
| Dec 12 | 2022-12-12 00:00:00 UTC | 2022-12-19 00:00:00 UTC | 0 | 0 | 0 |
| Dec 19 | 2022-12-19 00:00:00 UTC | 2022-12-26 00:00:00 UTC | 0 | 0 | 0 |
| Dec 26 | 2022-12-26 00:00:00 UTC | 2023-01-02 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2 | 2023-01-02 00:00:00 UTC | 2023-01-09 00:00:00 UTC | 0 | 0 | 0 |
| Jan 9 | 2023-01-09 00:00:00 UTC | 2023-01-16 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sourcesI love the simplicity of this idea because for lots of sites the database works just fine as a queue backend and it reduces the amount of infrastructure needed. I currently use https://github.com/dabapps/django-db-queue for https://devmarks.io which also uses the database to store tasks instead of a dedicated queue infrastructure. `Django Q` also has an option to use the database, but I haven't tested it at all: https://django-q.readthedocs.io/en/latest/configure.html#orm. And if you are already running `redis` for your site, https://github.com/rq/django-rq is another option.
The one benefit of this package is that it is async-first which will be beneficial as Django continually adds in more async capabilities. Nice work! I'm looking forward to trying this out and seeing how it works!
In Show HN: Chard – simple async/await background tasks for Django> It's easier to read for you.
It would be easier for me to read if everyone wrote their code in French. Is that a good enough reason to make the whole company switch?
There's subjectivity, and then there is "I'm not frustrated by having to dig for the return type of every function I call, so no one should using typing in their function signatures because I don't like to look at it".
> I run an agency ... up to ~100k lines of code each ... practically I have almost never had an experience like the one you describe in 20+ years of working on Python codebases.
You're either a genius who is able to maintain a huge graph of functions calls and typing in your mind, across multiple repos and many years, or your codebase is an absolute nightmare to work on (it could also be both, and you're just able to deal with it). If I interviewed at a compa
Read the rest
ny in 2022 and they told me they have multiple 100k+ line repos of untyped Python, I would run away as fast as possible, as would the coworkers that I value the most. The ones that wouldn't run away are the ones that think types are inconvenient and unit tests are annoying to write, which really aren't the people I enjoy working with.
Edit: if you want evidence, I pulled some examples from your profile.
I've never worked with Django, and let's pretend I'm onboarding at your company and need to get into your `django_dbq` repo.
You have a `Job.get_queue_depths()` method here: https://github.com/dabapps/django-db-queue/blob/23f8ebe80b66.... What does this return? Okay... it builds this `annotation_dicts` object from the objects in a `Job`, then filters them, gets the queue names, sorts them, then annotates them (?). `annotation_dicts` also seems to start with a `JobManager`, and I can't tell how/if it ends up actually being a `dict` of something, so I'm not sure if the name is right. Then we return a dict of name:queue_depth, okay good. I guess the keys to the dict are strings?... Wrong, they're `models.CharField`, and I only can find that because it happens to be in the same file/class.
If the function was typed, and mypy enforced, I would have `def get_queue_depths() -> Dict[models.Charfield, int]:` (assuming the value is an `int`, I also can't verify the `.annotate(Count(...))` returns an `int`...). This would have saved me all of that above, which is basically just doing static analysis in my head, and not adding any value to the business.