Apollo GraphQL Blog
medium.com/apollo-stack · Company blog · on HN since 2016
The Apollo team's Medium publication on GraphQL, covering the Apollo data stack, Apollo Server, query batching and static queries.
What HN saysHN commenters point to it as a good source on overall GraphQL architecture, though the given comments mostly discuss GraphQL APIs and access control in general.
19HN people shared it
3linked it in comments
30stories submitted
132story points
9 years agolast shared
2016people per year2026
Most-shared posts
- 1Query batching in Apollo5 people · 11 points · first shared 2016 · discussion on HN
- 2Introducing the Apollo GraphQL data stack4 people · 18 points · first shared 2016 · discussion on HN
- 3Apollo, the data stack for modern apps2 people · 9 points · first shared 2016 · discussion on HN
- 4Visualizing Facebook's take on querying the app data graph2 people · 7 points · first shared 2016 · discussion on HN
- 5Apollo Server 0.2: GraphQL with Express, Connect, HAPI or Koa2 people · 4 points · first shared 2016 · discussion on HN
- 6What every developer needs to know about GitHub’s new API1 people · 42 points · first shared 2016 · 1 comments on HN
- 7GraphQL is the new REST1 people · 11 points · first shared 2016 · 3 comments on HN
- 85 Benefits of Static GraphQL Queries1 people · 6 points · first shared 2016 · discussion on HN
- 9New features in GraphQL: Batch, defer, stream, live, and subscribe1 people · 5 points · first shared 2016 · discussion on HN
- 10React and GraphQL Tutorial Part 3: Mutations1 people · 3 points · first shared 2017 · discussion on HN
- 11GraphQL vs. Falcor1 people · 3 points · first shared 2016 · discussion on HN
- 12GraphQL Subscriptions with Redis Pub Sub1 people · 3 points · first shared 2016 · discussion on HN
- 13Rethinking data fetching for Angular apps with GraphQL1 people · 3 points · first shared 2016 · discussion on HN
- 14Reducing React re-renders and server roundtrips by profiling1 people · 2 points · first shared 2016 · discussion on HN
- 15GraphQL: 3 common questions from JavaScript devs1 people · 2 points · first shared 2016 · discussion on HN
What HN people wrote when they linked it
aturek · 2016-09-14
I'd love to hear how Github is doing ACL here. We came up with a pretty neat solution on my team, which we have not yet open-sourced, for JS. But it was a lot of first-principles design work; there don't seem to be any good examples.
This was pretty much all the documentation we had, and it's more a design analysis of edge-vs-node authorization: https://medium.com/apollo-stack/auth-in-graphql-part-2-c6441bcc4302#.h…
Edit: Our eventual solution looked a lot like
class SomeTypeOfResolver {
@allowIfAny(rule1, rule2, rule3)
someProperty;
@allowIfAll(rule4, rule5)
otherProperty = defineRetrieverFunction();
}
e1g · 2016-10-14
Perhaps http://graphql.org/blog/rest-api-graphql-wrapper/ might be useful. Also the Apollo team has a good blog with many articles on the overall GraphQL architecture https://medium.com/apollo-stack
niftich · 2016-09-14
> secure and scalable
> over the Internet
What does this really mean? How does this substantially differ from the now-facetious term 'web scale' [1] ?
Modern RDBMS'es offer encrypted communications between client and server [2][3][4], but nothing is stopping a deployer from putting a proxy between the database and the Internet-resident end-user to translate between authentication mechanisms. In fact, this happens in every single API today, where the Basic or OAuth or Cookie-Auth request comes in the HTTP body, and gets made into a database query in a query language the DB understands -- SQL or something else.
GraphQL needs to you bring your own authn/z [5][6][7] much the same way that your run-of-the-mill HTTP API needs to you to bring your own authn/z, so I can't accept 'secure' as an innovation over SQL. "Scalable?" How?
I genuinely think this tech is neat but let's consider what it gives you. GraphQL packages together the query language known as GraphQL, the IDL/typespec language known as GraphQL, the server spec known as GraphQL which a GraphQL-compliant server must implement [8], inside which you have to hook up your actual datastore to the GraphQL server [9][10][11][12]. It's a useful tool to build a client-server system where you're going to make a backend query in the end, but I wonder if its full potential will be realized when there are GraphQL-capable datastores to skip that extra data munging layer you have to implement yourself; but if SQL were passed on…