38 ms·
We just started using it for parts of our frontend API in production. We started with Graphene but it ultimately fell very short of our expectations, so I actua
by RussianCow 7y ago
We just started using it for parts of our frontend API in production. We started with Graphene but it ultimately fell very short of our expectations, so I actually wrote my own GraphQL library from scratch. It's far from spec-compliant, but it supports the bare minimum needed to be able to run queries and mutations, and provides a lot of performance escape hatches that most GraphQL libraries simply don't (like batched resolution for lists of items, as well as a pre-resolver step for big-picture optimizations).
I plan to open source it in the coming weeks. Email me if you're interested and I will reach out when it's on GitHub.
- true_religion 7y agoIs it based on the graphql core next library?
- RussianCow 7y agoI actually didn't know about this port, so no. It was originally built on graphql-core, but I found it difficult to use as a base for higher-level abstractions (not to mention it really is a 1-to-1 port of the JS lib and is thus incredibly un-Pythonic), so everything was written from scratch, including the parser. (Hence why it's not fully spec-compliant yet—a few GraphQL language features are still not implemented.)
- true_religion 7y agoWell,if that’s the case I’m very interested in it. I have been maintaining a private fork of graphene for a while, with a desire to improve performance but I’m stymied by having to go through graphql-core. All the python graphql libraries are based on it, so your work is going to be very valuable I expect.