Live data from Hacker News

Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

learnapollo.com

31–39 of 39 posts

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#31
post #14

All 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…

With regards to reducing the number of database fetches, DataLoader [1] (also by Facebook) is a great tool used by a lot of GraphQL severs to solve this issue.

[1] https://github.com/facebook/dataloader

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#32
post #14

All 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…

With regards to reducing the number of database fetches, DataLoader [1] (also by Facebook) is a great tool used by a lot of GraphQL severs to solve this issue. [1] https://github.com/facebook/dataloader

Very good point, mrpoller. DataLoader works great in combination with GraphQL. We're using a similar concept at Graphcool (which is written in Scala using Sangria). This method combined with a smart caching strategy turned out to be very effective.

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#33
post #14

All 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…

With regards to reducing the number of database fetches, DataLoader [1] (also by Facebook) is a great tool used by a lot of GraphQL severs to solve this issue. [1] https://github.com/facebook/dataloader

[deleted]

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#34
post #14

All 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…

They don't even seem to have a live site with a usable demo as far as I can see. If it does exist, it's buried deep where it shouldn't be.

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#35
Because they don't tell you on the site:

Apollo Client is a Javascript library that can be used in any front end where you want to use data from a GraphQL server.

It's incrementally adoptable, so that you can drop it into an existing JavaScript app and start using GraphQL for just part of your UI.

It uses TypeScript.

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#36
post #21

Earlier quoted context omitted.

In addition to graph.cool, there's scaphold.io. has any body used these two and can share their experience? (I'm not affiliated with either of them. Just wanna know)

Hey there, I've used both Scaphold and Graph.cool and I would thoroughly recommend Graph.cool. To understand why, I recommend you have a play with them yourself. It is immediately clear, in my opinion, that Graph.cool is a much better designed product in every aspect. Graph.cool's UX exudes refinement and quality that Scaphold's does not. An example of this is the fact they invite you to their Slack team automaticall…

This is incorrect on several points. Scaphold supports relay and Apollo out of the box and integrates with auth0 (per their docs; I've used neither feature).

Subjectively, having played with both, I chose scaphold (over graph.cool and reindex) for a few reasons:

- pricing model makes a lot more sense to me. Graph.cool tiers their pricing on user counts, which makes very little sense to me for a product the cost drivers of which are storage and throughput. They also apparently count a user once they register, with no clear way of handling inactive users (can't be good for your LTV calcs). Reindex was also suboptimal imo, with steep jumps from free tier to paid. They also charge based on 'operations,' which, while less so, also seems strangely divorced from what I imagine their cost drivers are. Scaphold seems to have taken firebase's pricing model, which was a smart move

- storage. Graph.cool has really low storage per tier. Reindex bills storage separately from 'operations' and only charges in $50 5GB chunks (5.1 GB last month? Sorry!). Scaphold again copies firebase's pricing with small, inexpensive increments.

- ui. I didn't use graph.cool's ui too much, but I'm very happy with scaphold's. Afaik reminded didn't have any ui to speak of--someone correct me here if I'm wrong. You can build your entire schema in scaphold's ui (with very helpful tool tips most of the time) , manage integrations (which, generally, just make certain queries/mutations available), and view some pretty thorough analytics on your app. Coming from firebase, which has been really neglecting web app users in favor of mobile lately (imo), this was really nice.

Lastly, I'm new to graphql, but as I understand it, scaphold has added some nice features on top of the API. It seems to mirror PostgraphQL (a postgres graphql utility), and adds pretty robust support for relationships (1:1,1:many,many:many). My schema is highly relational and, so far, it's a breeze.

I will note that graph.cool seems to have much more newbie-friendly docs, and maybe more comprehensive docs over all. Scaphold's docs are okay: they're wider than they are deep (maybe a paragraph for every feature w/ an uncommented snippet), there are some obvious mistakes, and some parts of the docs are scattered between the docs page and the UI's tool tips. When I had problems, though, their team got back to me w/in minutes (on email and slack).

To be clear, I'm not affiliated w/ any company discussed here--I'm just a user shopping for a firebase replacement.

That said, if you're considering the product, here's a ref link--$10 for you & $25 for me https://scaphold.io/referral?ref=99XXP3

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#37
post #21
post #14

All 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…

In addition to graph.cool, there's scaphold.io. has any body used these two and can share their experience? (I'm not affiliated with either of them. Just wanna know)

I tried Scaphold because all of the shiny promises on their landing page like: out of the box integrations, analytics etc.

Turns out the most basic feature of a BaaS app, the console, is practicaly unusable. Too buggy, too many errors happening. After struggling with it for a while I switched to graph.cool.

The small issues that I had with it were resolved by the team immediately. Smooth sailing from then on

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#38
post #36

Earlier quoted context omitted.

Hey there, I've used both Scaphold and Graph.cool and I would thoroughly recommend Graph.cool. To understand why, I recommend you have a play with them yourself. It is immediately clear, in my opinion, that Graph.cool is a much better designed product in every aspect. Graph.cool's UX exudes refinement and quality that Scaphold's does not. An example of this is the fact they invite you to their Slack team automaticall…

This is incorrect on several points. Scaphold supports relay and Apollo out of the box and integrates with auth0 (per their docs; I've used neither feature). Subjectively, having played with both, I chose scaphold (over graph.cool and reindex) for a few reasons: - pricing model makes a lot more sense to me. Graph.cool tiers their pricing on user counts, which makes very little sense to me for a product the cost drive…

Thank you for going so much into detail.

Our pricing structure has been like that since we started a year ago. We have learned a lot since then and you touch on some important points. We have put of updating the pricing model because we have been busy improving docs and working on the product, but expect a complete revamp early next year.

If you want to talk more you can always reach me on soren@graph.cool :-)

Re: Learn Apollo: Build GraphQL Apps with React, React Native or Exponent

#39
post #21
post #14

All 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…

In addition to graph.cool, there's scaphold.io. has any body used these two and can share their experience? (I'm not affiliated with either of them. Just wanna know)

I tried using Scaphold but the main issue is that their entire service is just so buggy. They try to do everything and then nothing works "really" well. It's actually because I got so disappointed, I was looking for other solutions and Graph.cool was the best that I could find. The best is their support. They are so highly responsive on their Slack channel, I rarely see that.
Post reply on HN