Re:Just use Postgres for everything
by phoebefactorial on Saturday December 10, 2022 @04:11PM
(#33936834)
I do Django freelancing and have had a fair amount of small clients with relatively few users. Adding workers and a message broker adds a lot of complexity over just a single Django server. I even had the thought to build something like this but looks like someone already did! Thanks for sharing this, looks like a great tool to know about.
Why not the battle tested celery?
Re:Just use Postgres for everything
by llIIllIIllIIl on Saturday December 10, 2022 @12:35PM
(#33934575)
Battle tested Celery has dropped the ball so many times during operations and updates, that I would be very uncomfortable giving that recommendation.
Here's a really good article
about why you might want to involve your database in queues (short version: transactions): https://brandur.org/job-drain
Re:Just use Postgres for everything
by scrollaway on Saturday December 10, 2022 @12:35PM
(#33934589)
See article?
But also, Celery has an awful DX. I think the question is more, why do I need celery when Postgres can do the job itself?
Currently integrating Procrastinate (https://procrastinate.readthedocs.io/en/stable/) to use Postgres as a job queue in a Django API backend.
Dropping dependencies is very nice especially when dealing with an MVP / small apps.