django-q VS django-webpack-loader

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 Webpack Loader

Check out https://github.com/django-webpack/django-webpack-loader

About one month ago i started having a lot of doubts on my frontend. At first, instead of decoupling frontend from backend, i decided to use a library called django-webpack-loader that lets me serve webpack from Django templates, so i created a Vue app and served it from Django (i used a simple index.html view). So at this point i basically have a SPA that instead of being decoupled from Django, it's served by Django.

You can do this with Django and nothing else easily or you can use a third party library called Django-Webpack-Loader.

In addition to what's already been said (completely separate frontend & backend; or do a CDN include), I've worked in a codebase that uses django-webpack-loader.

The biggest challenge to using Django with React IMO is getting the right blend of isomorphic rendering down. I don't want to go full SPA with Django as this defeats the purpose of Django IMO. Most parts of the site I want server-rendered, while in stateful parts I want React. So, let's say I have a site with 20 different React "apps" (i.e. stateful components) that I want to distribute amongst my various Django sections (Django "Apps" within the same project). And I want to do that with one webpackconfig. How do I tell my webpack where to put all those react bundles? The answer I've found is django-webpack-loader[1], however as you can see in the Issues section, one of the biggest limitations here is the inability to chunk React (and other issues).

Does anyone have a solution they like for this kind of isomporphic Django problem?

1. https://github.com/owais/django-webpack-loader