djmashko2

9 ms·

31.
by djmashko2 8y ago
Open source lead at Apollo here. Syrus is correct that it will have about the same performance as Node in these particular benchmarks. We are working on performance improvements for Apollo Server 2.0, but they are targeted at a totally diff
32.
by djmashko2 8y ago
Open source lead at Apollo here: The most important thing about the persisted queries approach highlighted in that article, compared to traditional REST architecture, is that the queries live in your _client_ codebase. So the frontend devel
33.
by djmashko2 9y ago
One really neat thing is that the clients are based on the MIT-licensed Apollo Client. So we hope that everyone using GraphQL can easily get these benefits! Check out the code on GitHub: https://github.com/awslabs/aws-m
34.
by djmashko2 9y ago
Note that "forever" here means "for as long as this specific browser tab is open", both for GraphQL and for Redux.
35.
by djmashko2 9y ago
Jonas Helfer gave a talk about this: https://www.youtube.com/watch?v=coU6OmISOBM
36.
by djmashko2 9y ago
You're in luck, there are libraries that can do it for you! https://github.com/stems/join-monster And even a system that generates your whole schema: https://github.com/postgraphql/postgraphql
37.
by djmashko2 9y ago
(Author of the post here) If you aren't yet familiar with GraphQL and the problems it solves, it might be better to watch the talk on YouTube, since it includes much more of an introduction from the start, plus more color and detail:
38.
by djmashko2 9y ago
> Because you can't possibly now what your API consumers use on their side. That's the best part - with GraphQL you _do_ know, since people have to ask for every single field they want.
39.
by djmashko2 9y ago
(Author of the post here) Thanks for the notes! > And immediately after that the article spends two pages of text explaining how insanely complex the "becomes easy with GraphQL" really is, and offers no actual details on the &q
40.
by djmashko2 9y ago
We've got one here you can try out, and I hope people build more! https://www.apollographql.com/engine/ (Disclaimer: I work on Engine)
41.
by djmashko2 9y ago
(Author of the post here) > GraphQL is above all, just an optimization. It optimizes the amount of bytes sent over the network. This was a common thought when GraphQL was first announced, but working with organizations that are adopting
42.
by djmashko2 9y ago
(Author of the post here) I think there are 2 differences: 1. It's very very easy to write a GraphQL query, since GraphQL comes with auto-completing tools to do so. Even non-technical staff at our company often use it to get informatio
43.
by djmashko2 9y ago
Hi, author of the post here! With GraphQL, you can think of each field as a tiny endpoint, and you do access control on that in the same way as before. It turns out that while GraphQL allows the frontend developers to select the data they n
44.
by djmashko2 9y ago
Hi sumobob! Sashko here - open source lead at Apollo I'm glad you've been having a great time using Apollo. I hope we've been up front with the idea that we have commercial products since the start, and I think monitoring and
45.
by djmashko2 9y ago
For sure - we've been super busy also organizing GraphQL Summit so it's been quite a week!
46.
by djmashko2 9y ago
Hi Blake! Unfortunately we did not have time to finish all of the redirects for the old site, so we have both versions up at the moment. I expect to have the redirects working properly by the end of the week, here is the new location for th
47.
by djmashko2 9y ago
The current license doesn’t prevent you from doing that in any way.
48.
by djmashko2 9y ago
Here's a page we put together with case studies of companies using GraphQL in production: https://www.graphql.com/case-studies/ There are articles from GitHub, Shopify, Artsy, Walmart, Coursera, New York Times, an
49.
by djmashko2 9y ago
New york times uses React: https://www.nytimes.com/
50.
Reify: Meteor's evolving JavaScript module compiler(blog.meteor.com)
2 points by djmashko2 9y ago|0 comments
51.
Using Scala.js with React and GraphQL(dev-blog.apollodata.com)
1 points by djmashko2 9y ago|0 comments
52.
by djmashko2 9y ago
Yeah, it's really unfortunate that people feel the need to trash other technologies when promoting something. I'm a big fan of GraphQL and tried to write up a more low-level comparison here: https://dev-blog.apollodata.
53.
by djmashko2 9y ago
Yeah the diagram is intended to represent where GraphQL usually sits in your architecture.
54.
by djmashko2 9y ago
Just did it, thanks so much!
55.
by djmashko2 9y ago
This is a great answer: https://news.ycombinator.com/item?id=14816423
56.
by djmashko2 9y ago
It's exactly the same thing but renamed - we're going to make both names work for a few weeks and then deprecate the graphql-server name after all the resources are updated. It's exactly the same, just change your import to &
57.
by djmashko2 9y ago
Hey, I'm on the Apollo team! As mentioned in the blog post, this is just a thin wrapper around the regular GraphQL.js implementation, with a few small bells and whistles added! The intention of this library isn't to change a lot a
58.
by djmashko2 9y ago
The thing is that the "all" is actually _not_ generic in this case. The GraphQL server implementor has to specify a field called that specifically.
59.
by djmashko2 9y ago
GraphQL definitely allows GET and supports HTTP caching just as well as any other kind of API!
60.
by djmashko2 9y ago
I think the parent is saying something different: They were happy with GraphQL for their API, but weren't happy with the requirements the Relay client library imposed. My interpretation is that they are now using a GraphQL API but fetc

More ›