waitress VS django-q

I have spent hours reviewing and testing ways of making waitress exit cleanly (like this and this) but the best I can do so far is a kind of suicidal SIGINT which makes Windows complain "the pipe has been ended" when stopping through the Services control panel, but at least it stops :-/ I guess the pythonservice.exe which pywin32 starts, should not terminate, just the waitress treads?

Waitress - for serving your application easily (pairs very well with Whitenoise).

If you’re delegating your load balancing to something else further up the stack and would prefer a simpler WSGI server than Gunicorn, Waitress is worth a look: https://github.com/pylons/waitress

Other options are DjangoQ and Huey, which tend to work ok. Of the two I prefer DjangoQ. Database backed, don't require the Redis/Celery rigmarole.

If you want a "simple" solution for sending email, the simplest that will likely last you the longest is using DjangoQ to create a background task that looks for model records that have not been emailed. Then use Sendgrid with an email backend to send them. You can use a library that already provides a Sendgrid email backend as well.

Take a look at Django-Q I was using it before moving to celery. Seems great just wanted experience with celery. Much simpler to get setup. Even use Django admin to schedule your tasks. Other option is a management command thats called using the full path of the python virtual env from a cron entry.

App Platform is a great concept, but we hit a dealbreaking road block when trying to migrate some Python apps with job queues. Their runtime (gVisor) doesn't support semaphore locks, which is used by Pythons multiprocessing and in turn used by most job runners (we discovered it with django-q, but I think most, if not all of them including Celery, rely on this, see link below).

The build times for Dockerfiles are also atricious… our build failed after 40 minutes by running out of memory and the multi-stage Dockerfile really wasn't anything special. We would have just used the images hosted on Github Container Registry, but App Platform only supports a limited range of Docker registries too. Note: the images build in 3 minutes on Github Actions.

As far as I can see it is also not possible to add any block storage too. While I mostly work on projects that use object storage anyway, SOME things just need persistent block storage. Which is annoying, since DigitalOcean HAS block storage… just not for App Platform.

I really wanted to use it, but man they make it hard.

https://github.com/Koed00/django-q/issues/522#issuecomment-1...

I use Django Q with ORM broker. Store tasks in db and retry if failed. You can also view/manage your queue in Django admin if you use ORM as broker (https://django-q.readthedocs.io/en/latest/brokers.html#django-orm).

django-q - Light weight task queue. When celery is too much over head.

Check out https://github.com/Koed00/django-q