graphql-python / graphql-python/graphene

Implement Dataloaders (N+1 issue) with middleware or follow docs example

Ouverte
#1,365 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
✨ enhancement
Langage dominant
Python
Étoiles
8.2k
Forks
818
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Hi all, I am trying to incorporate Dataloaders (https://docs.graphene-python.org/en/latest/execution/dataloader/) to our schemas to reduce load on our DB. However, I was wondering if anyone has had experience using either a [middleware](https://jerrynsh.com/solving-n-1-in-graphql-python-with-dataloader/) implementation vs. the ones outlined in the docs?

I also found that [saleor ](https://github.com/mirumee/saleor/blob/master/saleor/payment/dataloaders.py)uses a slightly different approach that is more similar to what was suggested by the docs. Just wondering if any1 has had experience using this feature in a bigger project.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Start by comparing the Graphene dataloader documentation with the linked middleware article and Saleor's dataloaders.py example. The issue does not identify a repository file, test, concrete implementation target, or definition of done, so the desired approach and completion criteria need to be established first.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
graphql, python
Domaine
api
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
15/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.