-
Notifications
You must be signed in to change notification settings - Fork 119
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
Should we investigate Apollo (GraphQL) ? #24
Comments
this would be great for someones 20% time ;) On the surface of things, it could cut the number of api requests we need to make. From reading the blog post it sounds like Github feel a shift from REST to GraphQL. Has anyone used it? I know its made by faceybook but could improve our apps in the future Resources: http://graphql-elixir.org/ |
I had spent little time on a PoC for HapiJS+GraphQL(Apollo)+REST API and React+Redux(with Apollo Tools) at Front End. https://github.com/pankajpatel/hapi-redux-graphql-rest It turned out to be a successful experiment and can accommodate the (legacy) REST APIs as well (to support legacy or recently developed systems). Now I have moved my app's REST API development with HapiJS+Mongoose to HapiJS+GraphQL+Mongoose. |
IMHO, the HTTP2 standard might be a game-changer as an alternate way to reduce REST latency. |
Found https://github.com/absinthe-graphql/absinthe + http://absinthe-graphql.org/ |
@des-des havent you used it recently? |
Briefly experimented with Absinthe (GraphQL) and Phoenix: @Jbarget we used GraphQL quite a bit at TC: https://github.com/dwyl/learn-graphQL |
and http://githubengineering.com/the-github-graphql-api/
relates to #18
The text was updated successfully, but these errors were encountered: