3 ms·
Issues with GraphQL - - the GQL server in practice is still going to have fixed contracts/endpoints, because arbitrary queries are a risk. This is what FB reco
by dirkg 9y ago
Issues with GraphQL -
- the GQL server in practice is still going to have fixed contracts/endpoints, because arbitrary queries are a risk. This is what FB recommends as well
- there is no help in actually implementing the server end to end, since its just really a wrapper over the actual calls that need to be made. Apollo seems to be the new standard way to do this.
- Mutations/subscriptions are still a work in progress
- maktouch 9y agoI agree that subscriptions are a work in progress, but how is mutations is a work in progress? Pretty sure it's defined and it works pretty well.
- marktani 9y agoEven though subscriptions are very much in progress from a specification point of view, the community came up with different approaches that are already employed in practice. Here are some additional resources: - RFC for GraphQL subscriptions: https://github.com/facebook/graphql/pull/267 https://github.com/facebook/graphql/pull/267 - How to use Subscriptions in GraphiQL: https://dev-blog.apollodata.com/how-to-use-subscriptions-in-graphiql-1d6ab8dbd74b https://dev-blog.apollodata.com/how-to-use-subscriptions-in-... - Using GraphQL Subscriptions with Apollo: https://www.youtube.com/watch?v=wo9XFmW0W2c https://www.youtube.com/watch?v=wo9XFmW0W2c If you want to use GraphQL subscriptions right now, I encourage you to try out our demo over at https://demo.graph.cool/worldchat/ https://demo.graph.cool/worldchat/. I work at Graphcool :)