graphgate
graphgate copied to clipboard
async-graphql
How production ready is this current project?
Hi! Big fan of async-graphql and rust here...
Seems that is lacking some maintaince (not sure) and some documentation... Is this already being used in production?
Hi! Big fan of async-graphql and rust here...
Seems that is lacking some maintaince (not sure) and some documentation... Is this already being used in production?
I use it for some "production" like things and plan on moving it forward to production, but I concur with @sunli829 here. Unless your willing to dig into the code and do some of your own maintenance, it may not be worthwhile. It ends up being worthwhile for me since Apollo went to the Elastic License.
we've been using it for the majority of production traffic for the last 9 months, currently running off the enum-variable-fix branch. Only minor issues are error reporting from downstream federated services, there was recently a PR to fix some of these issues, as well as missing some logging for debugging purposes. The logging issue i am looking to fix with another PR. But performance and reliability are very both very strong
I use own fork https://gitlab.com/oss47/graphgate - if someone else is interested, we can use and maintain it together.
It's also available in docker registry: registry.gitlab.com/oss47/graphgate
cc: @cawfeecoder @dhendrie91 @arthurfiorette
@Miaxos @dbanty - me and @jgautheron are willing to support graphgate.
We think that it will be better to not use own repos, or another organization, but to maintain it here in async-graphql org.
We can't reach to @sunli829 so far - maybe you can make a decision and if you agree, add us as maintainers to this project?
me and @jgautheron are willing to support graphgate.
Awesome!!
We think that it will be better to not use own repos, or another organization, but to maintain it here in async-graphql org.
I do agree with you!
We can't reach to @sunli829 so far - maybe you can make a decision and if you agree, add us as maintainers to this project?
I can't make a decision about this. I'm sure @sunli829 will see your message soon!
After doing quite a bit of wrangling to get Apollo Router into a state where I can run it in AWS Lambda (https://github.com/codetalkio/apollo-router-lambda), I'm quite curious for alternatives.
What has everyone's experience been with GraphGate so far, and does it only support Federation v1 or also v2?
Quite a few companies (and not small ones) have used it at scale, in its current state it doesn't support Federation v2, I'm working on a v2 implementation in a fork. Realistically I wouldn't use graphgate for Lambda requests because there's no static schema possibilities (only dynamic). It's relatively easy though to implement!
