-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How production ready is this current project? #23
Comments
I don't recommend it for production unless you can maintain it yourself.🙂 |
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 |
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 |
@Miaxos @dbanty - me and @jgautheron are willing to support graphgate. |
Awesome!!
I do agree with you!
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. |
We're working on a fork here: https://github.com/graphgate/graphgate, contributors welcome! |
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?
The text was updated successfully, but these errors were encountered: