rq VS django-rest-framework

Most of the small python alternatives I've seen use Redis as backend:

- https://github.com/rq/rq

That's pretty cool. Reckon it would work with existing code that calls Redis over the wire for RQ?

  https://python-rq.org

https://github.com/rq/rq is to the rescue.

We use RQ[0], it has Redis as a dependency. It’s pretty straightforward and we’re very happy with it. If you are using Django you may want to look at Django RQ[1] as well. RQ has built in scheduling capabilities these days, but historically it did not so we used (and still use) RQ Scheduler[2] which I think still has some advantages over the built in stuff.

[0] https://python-rq.org/

Also had a similar experience using RabbitMQ with Django+Celery. Extremely complicated and workers/queues would just stop for no reason.

Moved to Python-RQ [1] + Redis and been rock solid for years now.

[1] https://python-rq.org/

Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq

The GitHub Discussion: link

Django’s "batteries-included" philosophy makes it an excellent choice for API development. With Django REST Framework (DRF), you get:

I am maintaining a Python codebase that is based on Django and Django REST Framework (DRF). The codebase uses Nix for development, testing, CI/CD and packaging.

Django Rest framework

Explore the Django REST Framework Documentation for advanced topics.

I've seen some companies using React with Django REST Framework [1], to keep the benefits of Django (I'm not a Django dev so I will have to guess, the ORM and project structure?) while having a strong separation between front and back (separate projects, teams, deploys, etc).

[1] https://www.django-rest-framework.org

Django REST Framework is a powerful and flexible toolkit for building Web APIs using Django, the popular high-level Python web framework. Zuplo proudly sponsors the DRF project to continue improving the Django API development ecosystem.

I think people tend to consider Django either for building old-school, industrial-strength monolith apps or for APIs and using something like React for the front-end. I’m here to tell you that plain old Django is a great option even for your personal websites! In my opinion, if you need a database, you should use Django1.

This post will extend Django REST Framework's ViewSet and SimpleRouter to provide a Rails-like request handler class + resource routing in server-render Django applications. It also features form-level method spoofing for PUT, PATCH and DELETE requests via custom middleware.

Django Rest Framework