Re:Why do we need Flask, Celery, and Redis? (2019)
by rollingbarreler on Saturday April 18, 2020 @09:44AM
(#22907672)
Transactionality is enough for most systems. Your order either succeeds or fails, it never stays in an incomplete state. Queues are not a panacea, and introduce their own problems like obscuring problems by delaying them long enough to bring everything to a halt.
[ Parent
| on HN ]
Re:Why do we need Flask, Celery, and Redis? (2019)
by mattbillenstein on Saturday April 18, 2020 @08:17PM
(#22912281)
Yes, you wouldn't do all work in the task queue - commonly, we make some change in the database which can happen pretty fast, and after that transaction commits, we might defer a task that sends a notification, email, whatever.