django-q VS django-rest-framework

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 Rest Framework has no async support? https://github.com/encode/django-rest-framework/issues/7260

A URL shortener is a service that transforms long and complex URLs into short, easily memorable ones. This tutorial guides you through creating a URL shortener using Django REST framework and Postgres, deploying it on Koyeb.

Now, I'm converting this app into a Vue-based SPA (still powered by Django). I'm using the Django REST Framework to build the API that the SPA will interact with. (I'll be using token-based auth, via django-rest-knox. ETA: I'll actually be using djangorestframework-simplejwt.)

For the backend, we chose Python, Django Rest Framework. On the frontend, React, Redux, Saga, Sass. Let’s start with the backend, which was managed by Yegor. He writes about the server part of the project himself.

With regard to JSON API aspects of Django, have you used https://www.django-rest-framework.org/ ? I find it to be very satisfactory.

django-rest-framework and the Fetch API, or

Django REST Framework (DRF) Django REST Framework is a famous, powerful, and flexible toolkit for building Web APIs in Django. It provides a set of reusable components and tools to simplify API development, including serialization, authentication, permissions, and view sets.

I wish Django would take async more seriously. This comment gives a pretty good overview of the current situation (some points are more valid than others): https://github.com/encode/django-rest-framework/discussions/...

The Python ecosystem is strange. Where other dev communities will embrace new ways of doing things faster than most people can keep up — the Python community needs to be pulled kicking and screaming into the light once ever decade or so. Python 2 to 3, ~10 years.

async/await has been in Python since 2015, it feels like it's going to be another 5 years before we see people taking async seriously in the big packages. Same problem we had during the 2/3 transition. No library support, no developer support.

Thanks for helping Steve to complete his REST API, he is now partying🥳. You can get more information on how to use the Django REST framework to best way read the documentation. There are many alternatives to the Django REST framework, you can give them a try if you want,

[Django Rest Framework](https://www.django-rest-framework.org/) has the very nice idea of a [ViewSet](https://www.django-rest-framework.org/api-guide/viewsets/#modelviewset) that allows really minimal code to perform all the basic CRUD actions on a model.