What is Graphene?
Who uses Graphene?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Graphene in their tech stack.
Python's GraphQL version – Graphene – has some critical disadvantages, that we found critical:
- Lack of code optimisation. It is also hard to write optimized code because of graphene node API.
- Nonsecure by default. By using reversed fks, you can get a lot of extra data. To stop this, we have to explicit exclude wrong fields, which seems to be error prone.
- Nonflexible code structure. You can't make abstract
graphene.ObjectType class, this limits us a lot.
These are some reasons, that make us move to Django REST framework .
- Easy to use: Graphene helps you use GraphQL in Python without effort.
- Relay: Graphene has builtin support for Relay
- Django: Automatic Django model mapping to Graphene Types. Check a fully working Django implementation