django-q VS django-ninja

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

Django Ninja [1], it forever changed how I write Django project, in a way so elegant and productive.

[1]: https://django-ninja.dev/

Django Ninja is a RESTful wrapper for Django, while UtilMeta Python Framework uses a more concise declarative ORM Schema for Django and other future-supporting ORMs like sqlachemy and Peewee to build RESTful APIs more efficiently, and supports not only Django but all Python mainstream frameworks like Django, Flask, Starlette, FastAPI, Sanic, Tornado, etc.

I can't recommend [django-ninja](https://github.com/vitalik/django-ninja) enough. It's an easy to use, extremely fast, typed API for django. I've found it to be better in almost all aspects when compared to djangorestframework.

It's gaining popularity but is still widely unknown.

> The only place I really see Django at large companies is as an api using DRF or something.

This is not a bad thing. Using Django as an API backend is amazingly fast in terms of development time, especially with modern frameworks such as django-ninja [1].

Just use the built-in ORM to create models, write your endpoints, and use the built-in admin interface to play with the database if you don't have endpoints for everything.

There is also a less known feature of Django called admindocs [2], which automatically generates a human readable, hyperlinked documentation for your models and relations between them.

[1] https://django-ninja.rest-framework.com/

[2] https://docs.djangoproject.com/en/4.2/ref/contrib/admin/admi...

Personally, I also prefer django-ninja to DRF.

Actually that's not fully true. If you mix async and sync codes in django-ninja there will be some errors. Where's the proof ? django-ninja doesn't support async auth

Subscribe to this issue :D

Also recommend Django-Ninja. It basically reimplements fastapi's type and decorator-based API construction, but embedded directly in django so you have access to django's ORM and middleware library.