Skip to content
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

Open
nelsonic opened this issue Sep 30, 2016 · 6 comments
Open

Should we investigate Apollo (GraphQL) ? #24

nelsonic opened this issue Sep 30, 2016 · 6 comments
Labels
help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue

Comments

@nelsonic
Copy link
Member

nelsonic commented Sep 30, 2016

@nelsonic nelsonic added help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue labels Sep 30, 2016
@Jbarget
Copy link
Member

Jbarget commented Mar 31, 2017

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/
https://hexdocs.pm/plug_graphql/readme.html
https://www.infoq.com/news/2016/10/graphQL-GitHub

@pankajpatel
Copy link
Member

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.

@markhu
Copy link
Member

markhu commented Mar 31, 2017

IMHO, the HTTP2 standard might be a game-changer as an alternate way to reduce REST latency.

@nelsonic
Copy link
Member Author

nelsonic commented Jun 5, 2017

@Jbarget
Copy link
Member

Jbarget commented Jun 5, 2017

@des-des havent you used it recently?

@nelsonic
Copy link
Member Author

nelsonic commented Jun 6, 2017

Briefly experimented with Absinthe (GraphQL) and Phoenix:
https://github.com/nelsonic/phoenix-absinthe-graphql-api
but did not see the benefit as Channels (RealTime/PubSub) is not yet available.
Created follow up issue: dwyl/phoenix-todo-list-tutorial#19

@Jbarget we used GraphQL quite a bit at TC: https://github.com/dwyl/learn-graphQL
Again, I was put off by the lack of subscriptions. While they are in the spec:
https://facebook.github.io/graphql/#sec-Subscription-Operation-Definitions
Most implementations do not have the feature yet. ⌛️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue
Projects
None yet
Development

No branches or pull requests

4 participants