graphene-django VS Graphene

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.

And gqlgen is not alone in this. We found several more GraphQL frameworks that don’t take it upon themselves to address this problem. Widely used GraphQL server implementations, such as graphql-go/graphql and Python’s graphene, have the exact same gap of exposing messages of unexpected errors by default.

There are multiple Python-based GraphQL libraries and they all vary slightly from each other. For the longest time, Graphene was a natural choice as it was the oldest and was used in production at different companies, but now other newer libraries have also started gaining some traction.

> But you need to know that Wasmer and its sibling projects will stay free forever. We are open source lovers, all of us, and we have a strong background on working on open source projects before joining Wasmer too.

That's great. I'm sure the closed source paid 10x faster editions of the graphene Python GraphQL server written by Syrus "CEO of Graphene" and CEO of wasmer will be open sourced in this spirit.

https://github.com/graphql-python/graphene/issues/268#issuec...

http://graphql-quiver.com/

CloudinaryField is a custom model field not a django built in one and graphene-python doesn't know what do with it. See the list of types it does https://github.com/graphql-python/graphene/tree/master/graphene/types

Thanks for the reply, I was looking at Strawberry a bit but not enough documentation for a graphql noob like me... Hate to turn this into tech support but could you potentially answer a question for me? I'm having a really hard time figuring out how to do this. Given this example: https://github.com/graphql-python/graphene/blob/master/examples/simple_example.py and a slight modification:

Graphene was one of the first (if not the first) lib built on top of graphql-core to provide an easy to use api to build graphql applications. It's been around since 2015 and has a lot of integrations built for it (e.g. Django, SQL Alchemy, etc).