Hacker News Reader

Battle tested Celery has dropped the ball so many times during operations and updates, that I would be very uncomfortable giving that recommendation.

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?

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