From the creator's of Meteor. What kind of long-term commitment plan do you have for Apollo?
Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
11–20 of 39 posts
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#12From the creator's of Meteor. What kind of long-term commitment plan do you have for Apollo?
related Q: is it fair to think of this as your pivot from "ecosystem" to "chain of tools" and you needed new branding to make space for this?
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#13Hey :-) we just announced this. Happy to answer any questions. Here's the accompanying blog post https://dev-blog.apollodata.com/learn-apollo-build-graphql-a...
Can you give a comparison between Apollo Client and Relay? And if you know about upcoming Relay 2 features, I'd like to hear about it too in the context of Apollo Client.
If you have time, I would love to hear about your (and everybody else) opinion/prediction where we're going with client data management/server communication in the future. What's your take on client databases?
Thanks!
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#14All these GraphQL solutions seem to focus on the frontend and assume there's a magical GraphQL server somewhere. But GraphQL Just shifts the hard work from the client to the server and I haven't seen any good solution towards security (except storing all the possible queries a user may access, which kind of defeats the purpose of GraphQL in the first place) and performance (a large query is usually resolved to thousands of database fetches, instead of 1 optimized one) on the server side.
What we really need is a decent GraphQL server. The client isn't difficult anyway.
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#15All these GraphQL solutions seem to focus on the frontend and assume there's a magical GraphQL server somewhere. But GraphQL Just shifts the hard work from the client to the server and I haven't seen any good solution towards security (except storing all the possible queries a user may access, which kind of defeats the purpose of GraphQL in the first place) and performance (a large query is usually resolved to thousa…
The article was written by Graphcool. They provide a GraphQL Backend As A Serivice. I used Graphcool on a recent hackathon, and it was a pleasure to use. I rarely got going with a service as quickly, though I must admit that I had some GraphQL experience prior, which certainly helped.
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#16All these GraphQL solutions seem to focus on the frontend and assume there's a magical GraphQL server somewhere. But GraphQL Just shifts the hard work from the client to the server and I haven't seen any good solution towards security (except storing all the possible queries a user may access, which kind of defeats the purpose of GraphQL in the first place) and performance (a large query is usually resolved to thousa…
That's a really good point, kabes.
At Graphcool (https://www.graph.cool) we're working on exactly what you're describing. We're putting a lot of work into optimizing for the best possible performance while providing a powerful and flexible API. The key for this will be combining GraphQL and serverless technologies like AWS Lambda to implement your business logic.
Concerning security: We're currently testing a new permission system with a group of beta testers which leverages the Graph structure of your backend to specify data access rules.
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#17All these GraphQL solutions seem to focus on the frontend and assume there's a magical GraphQL server somewhere. But GraphQL Just shifts the hard work from the client to the server and I haven't seen any good solution towards security (except storing all the possible queries a user may access, which kind of defeats the purpose of GraphQL in the first place) and performance (a large query is usually resolved to thousa…
[deleted]
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#18From the creator's of Meteor. What kind of long-term commitment plan do you have for Apollo?
Hi - Sashko here, manager of open source at Meteor Development Group.
We're committed long term to Meteor and Apollo both, and view both technologies as critical to the long-term success of the company. Apollo originated as a project to improve the internal data system of Meteor, but we saw that it was useful in a wider context. Today you can use Apollo with Meteor or with any other JavaScript or native mobile technology.
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#19From the creator's of Meteor. What kind of long-term commitment plan do you have for Apollo?
Thanks, I didn't know that. That certainly explains the high polished look of Apollo combined with the seemingly non-existent business model.
I tried Apollo Optics - horrible brand name BTW, everyone I mention it to here in Germany thinks of the eyeware retailer - and while it was easy to integrate and nice to look at, it provided little actual value compared to existing tools in the same space of performance monitoring.
Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent
#20From the creator's of Meteor. What kind of long-term commitment plan do you have for Apollo?
related Q: is it fair to think of this as your pivot from "ecosystem" to "chain of tools" and you needed new branding to make space for this?
We decided to ship Apollo under a different name to avoid people's preconceptions that a tool released by the creators of Meteor would only work inside the Meteor platform. What we are seeing is that the JavaScript community has been consistently moving towards focused, decoupled tools, and it made sense to build Apollo in that way. Meteor has also received many improvements to make it easy to work with npm packages, new JavaScript features, etc.