graphene-django VS django-rest-framework-simplejwt

Graphene-Django Graphene-Django is a powerful library that integrates the GraphQL query language with Django, allowing for the development of flexible and efficient APIs. It seamlessly combines the expressive power of GraphQL with the simplicity and elegance of Django, enabling us to design APIs that fetch only the data the clients need.

Install Graphene and Graphene-Django. Graphene is a tool that makes working with GraphQL in Python easy, while Graphene-Django adds some additional abstractions to make adding GraphQL functionality to your Django project a breeze. To install Graphene and Graphene-Django, run the following on your command line/terminal, pip install graphene graphene-django.

But if you must take a look graphene for graphql. https://docs.graphene-python.org/projects/django/en/latest/

You will find a lot of videos about Django on YouTube. If you need a REST API try DRF. If you want GraphQL try Graphene Django. For WebSockets there is Channels. If you don't want to bother with having an API for your frontend but you still want that SPA feeling try HTMX.

I've used Graphene + Graphene Django to write GraphQL APIs for several years now, but graphene-django unfortunately seems to (mostly) be abandoned now.

In conclusion, the Graphene-Django library makes it easy to get started with GraphQL integration by allowing you to use your existing Django models as the data source for your GraphQL API and automatically generate the schema. For more information, check out the documentation.

Django ninja strawberry Graphene

in my last project I used graphene to build a Django backend application with GraphQL. It seemed like the best framework to adopt graphql in python at that time in terms of stability and maturity.

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.)

Django REST Framework SimpleJWT Django REST Framework SimpleJWT provides JSON Web Token (JWT) authentication for Django REST Framework APIs. It enables secure and stateless token-based authentication, allowing clients to authenticate and access protected endpoints.

I'm using simple JWT with DRF.

So , i was using djangorestframework-simplejwt for token bases authentication with drf.

I used JWT authentication instead. https://github.com/jazzband/djangorestframework-simplejwt

First: the drf token is not a jwt. If you want to use jwt, I recommend the drf simple jwt plugin: https://github.com/jazzband/djangorestframework-simplejwt

There is an issue in the drf-simplejwt repo that I borrowed some code from: https://github.com/jazzband/djangorestframework-simplejwt/issues/71.Is anyone doing authentication with JWT / HttpOnly cookies in a similar way? Thanks for anyone that can take a look or offer some feedback!

I'm not going to go in-depth with it, but I've seen a different technique used to achieve the same result in the SimpleJWT project that can be found in this file in the source code. Basically the technique relies on the settings_changed signal to establish default values for settings and update those settings in the context of the package. I'm not sure if there is a massive improvement on this approach over the previous one (maybe caching?), but if there is, feel free to comment.

I work in FOSS and have a project I can share with that stack. The back-end is here. Change the branch to develop and look in accounts. Its not a perfect example of what you want since we extend the TokenView with VogonTokenVerifyView. Basically you create a login form on your front-end and then make a request to TokenObtainPairView with the login info and it will return tokens if everything went to plan. The vue project can be found here. There is really nothing fancy happening in the frontend, create a form and send the information. I would not save the tokens in localStorage like we are doing. This is a very debated topic but I have come to the conclusion after tons reading on the subject that cookies are a better route. There is an interesting thread on the subject in a pull request in the simplejwt-repo. Once that pull request is merged, we will switch to cookies.