Coming from Laravel, only thing I miss is native Jobs/Queues for background processes.
They are not native indeed but I suggest you look at django-rq which as far as I know are still one of the simplest ways to add a queueing system to a Django application.
If there's one thing I learned by using multiple programming languages in my career is not to try to bend one framework to be similar to another. Just embrace it :-)
Django is (mostly) function based, I think it's normal that django-rq is as well.
Are you having specific issues/limitations with using django-rq as is?
No not really. A Django codebase has just been thrown at me 😅
There's a module which sends number of emails so I thought why not do it in background.
Right now, I am just trying to figure out things using Laravel knowledge and googling.
Nice!
They are not native indeed but I suggest you look at django-rq which as far as I know are still one of the simplest ways to add a queueing system to a Django application.
Yeah I found it while doing my research. Thanks.
Is it only possible to enqueue functions? 🤔
What do you mean?
In Laravel we have Job classes which we dispatch. But in django-rq, it seems like it's only possible with functions.
If there's one thing I learned by using multiple programming languages in my career is not to try to bend one framework to be similar to another. Just embrace it :-)
Django is (mostly) function based, I think it's normal that django-rq is as well.
Are you having specific issues/limitations with using django-rq as is?
No not really. A Django codebase has just been thrown at me 😅
There's a module which sends number of emails so I thought why not do it in background.
Right now, I am just trying to figure out things using Laravel knowledge and googling.
Good luck :)
Thank you 🙏