News for hackers. Stuff that matters.
Re:Why do we need Flask, Celery, and Redis? (2019) by lifty on Saturday April 18, 2020 @08:36AM (#22907290)
I agree. That is why I stopped using languages that have a poor concurrency story. Also, using an external queue and workers considerably increases the operational complexity of the system. An in-process solution with some light persistence for the work queue in an embedded database can go along way, at least until you outgrow a single machine. Doing both ops and development I’ve learned to appreciate simple solutions.

There are no comments on this comment yet.