Top all-time · #1406
dev-blog.apollodata.com
Company blog · dev-blog.apollodata.comprogrammingweb
dev-blog.apollodata.com is the company blog at dev-blog.apollodata.com, writing about programming and web. Since 2016, 51 different Hacker News readers have linked it 84 times, most often “Apollo Client 2.0”. It is still writing: the last post was on 2026-10-07, and you can follow it by feed.
Too few sampled comments (27) to say how often HN recommends it.?
Why HN links it
HN readers link Apollo's dev blog for GraphQL technical material: client and server query optimisation, persisted queries, subscriptions, GraphQL vs REST and Falcor comparisons, and Apollo Client 2.0 and state management.
Summarised by Claude from a sample of 27 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Unlock the power of GraphQL and master modern APIs with the official Apollo GraphQL blog: tutorials, best practices, & cutting-edge insights.
Most-linked posts?
- /the-future-of-state-management-dd410864cae23 people · 3 mentions · first linked 2018-03-01
- Apollo Client 2.03 people · 3 mentions · first linked 2017-10-25
- GraphQL vs. REST3 people · 3 mentions · first linked 2017-07-24
- Introducing Launchpad: The JSFiddle for GraphQL Servers3 people · 3 mentions · first linked 2017-05-18
- /persisted-graphql-queries-with-apollo-client-119fd7e6bba53 people · 3 mentions · first linked 2017-10-02
- Exploring Relay Modern: About the Latest RC of Facebook’s JavaScript GraphQL Client2 people · 2 mentions · first linked 2017-04-19
- 5 benefits of static GraphQL queries2 people · 2 mentions · first linked 2016-10-25
- /2 people · 2 mentions · first linked 2017-04-21
- Securing Your GraphQL API from Malicious Queries2 people · 2 mentions · first linked 2018-02-22
What Hacker News says?
Meteor Development Group | Open Source Engineers, Back-end Engineers, Front-end Engineers | San Francisco, CA | Full-time, Onsite and Remote Back-end Engineers: Build the foundations and APIs of our tools for GraphQL and JavaScript developers. You'll have the opportunity to learn and use the most cutting edge technologies as you help shape and deliver the components that make up our commercial cloud services, Optics…
Comment linking /
on “Ask HN: Who is hiring? (June 2017)”Submitted Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client as a story · 354 points
HN discussionIf you're interested in front-end development, there are a few companies which focus on that: - Apollo/Meteor: https://dev-blog.apollodata.com/ - Auth0: https://auth0.com/blog/tech/ - Chroma: https://blog.hichroma.com/ - LogRocket (my company): https://blog.logrocket.com/
Comment linking /
on “Ask HN: Which companies have the best blogs written by their engineering team?”Submitted The GraphQL stack: How everything fits together as a story · 210 points
HN discussion> You'll also lose a lot of control over your queries which was a big reason for me to move from Django/Rails/etc. style tools to trying out GraphQL. For restricting queries, an option is using persisted queries (e.g. https://dev-blog.apollodata.com/persisted-graphql-queries-wi... ). The idea is nice, having full control in development while locking down allowed queries in production. You'd still have to deal with t…
Comment linking /persisted-graphql-queries-with-apollo-client-119fd7e6bba5
on “Hacker News Clone Using GraphQL and React”Submitted Apollo Client 2.0 as a story · 164 points
HN discussionGateway APIs: http://microservices.io/patterns/apigateway.html Assuming you've read that then I'd add the following. If you don't have something approaching a gateway, you're probably doing a big disservice to your users (assuming clients fetch data via API, rather than using a traditional render-on-the-server framework like Django or Rails). The value proposition of GraphQL is based on the assumption you're already…
Comment linking /optimizing-your-graphql-request-waterfalls-7c3f3360b051
on “gRPC-Web: Moving past REST+JSON towards type-safe Web APIs”Submitted Apollo Server 1.0 – GraphQL Server for Node.js Frameworks as a story · 159 points
HN discussionHi, I'm from the Apollo Client team. We're going to write some more content in the coming days or weeks about the differences, but here are some of my main thoughts based on following along during Relay Modern development: 1. Relay uses a build process to generate code for queries. That allows some better performance optimizations and static typing out of the box. However, it prevents you from doing anything which r…
Comment linking /5-benefits-of-static-graphql-queries-b7fa90b0b69a
on “Relay Modern: Simpler, faster, more extensible”Submitted Apollo Client 0.5 as a story · 62 points
HN discussionYes, now that you mention it, I do remember hearing about Falcor. For anyone that's interested I found this comparison: https://dev-blog.apollodata.com/graphql-vs-falcor-4f1e9cbf75...
Comment linking /graphql-vs-falcor-4f1e9cbf7504
on “GraphQL Patent Infringement Issues”Submitted One GraphQL Client for JavaScript, iOS, and Android as a story · 30 points
HN discussion> - However the worst thing so far to me has been i have watched as UI developers go from writing simple rest queries, and doing a bit of work on the front-end to writing extremely inefficient and convoluted queries. Even worse is when a third party is doing it and i have no say over what they do with it. To your last point, there are a few ways you can provide feedback on or limit the cost of your queries. I'd reco…
Comment linking /securing-your-graphql-api-from-malicious-queries-16130a324a6b
on “How to GraphQL – A Fullstack Tutorial for GraphQL”Submitted The next step for realtime data in GraphQL as a story · 13 points
HN discussionI'm genuinely surprised by the number of people on HN who seem to know very little about what has been safe to call the successor to REST for quite some time. Forgive me if this sounds hyperbolic, but unless you have unusual or strict requirements, building a new app in 2017 REST-first is most likely a terrible mistake. Let me clear up some misconceptions I see in almost every HN comment thread on GraphQL: 1. GraphQ…
Comment linking /new-features-in-graphql-batch-defer-stream-live-and-subscribe-7585d0c28b07
on “Ask HN: What tech that's right around the corner are you most excited about?”Submitted Reducing Our Redux Code with React Apollo as a story · 12 points
HN discussionCheck out this article [1] (or video) on Dan Schafer's talk, on how they use Dataloader and GraphQL internally at Facebook. Covers most of it. To summarize, they create a class for each GraphQLType which has their own "gen" function such that it is the only way to generate data. This way you get a single source of truth. There's also a video of Lee Byron going through Dataloader's source code which was pretty fun to…
Comment linking /graphql-at-facebook-by-dan-schafer-38d65ef075af
on “The GraphQL stack: How everything fits together”Submitted Apollo 1.0 is coming – GraphQL for React, Angular and co as a story · 5 points
HN discussionIt got more approachable for me when I started to think about it as a specific "backend for frontend" pattern. I don't see it as a _real_ competitor to REST, even though it's trying to market itself this way. I think recent "@rest" addition from Apollo ( https://dev-blog.apollodata.com/apollo-client-2-0-5c8d0affce... ) shows they can easily live together - backend uses REST and frontend can rely on GraphQL.
Comment linking /apollo-client-2-0-5c8d0affcec7
on “The GraphQL stack: How everything fits together”Submitted 5 benefits of static GraphQL queries as a story · 5 points
HN discussionHere's a high-level article about performance in general, but it shows how a UI and query could map to (for example) a function-driven API (this could be local to the server or remote): https://dev-blog.apollodata.com/optimizing-your-graphql-requ... Examples more specific to a particular backend technology feel redundant because my assumption is that once you're in the land of calling functions, we don't need to hol…
Comment linking /optimizing-your-graphql-request-waterfalls-7c3f3360b051
on “React, Relay and GraphQL: Under the Hood of the Times Website Redesign”Submitted Apollo Link: The modular GraphQL network stack as a story · 4 points
HN discussion(I work on Apollo) It's hard to know exactly what will be included in Relay 2, so we'll have to wait to make a comparison. Apollo came after Relay 1, and so has been designed with a few key differentiators: (1) flexibility, since it's built in a modular way and has a lot of hooks into internals, (2) less opinions, because it works with any GraphQL server and doesn't require a particular type of schema, and (3) optim…
Comment linking /apollo-client-developer-tools-ff89181ebcf
on “Learn Apollo: Build GraphQL Apps with React, React Native or Exponent”Submitted Introducing Launchpad: The JSFiddle for GraphQL Servers as a story · 4 points
HN discussionHey :-) 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...
Comment linking /learn-apollo-build-graphql-apps-with-react-react-native-or-exponent-4787269a4747
on “Learn Apollo: Build GraphQL Apps with React, React Native or Exponent”Submitted Introducing Launchpad: The GraphQL server demo platform as a story · 4 points
HN discussionProbably best to link to the blog announcement, https://dev-blog.apollodata.com/introducing-launchpad-the-gr... , to give context of what this is about, instead of directly into the launchpad UI.
Comment linking /introducing-launchpad-the-graphql-server-demo-platform-cc4e7481fcba
on “Launchpad: JSFiddle for GraphQL servers”Submitted Exploring Relay Modern: About the Latest RC of Facebook’s JavaScript GraphQL Client as a story · 4 points
HN discussionA few articles on the same topic: https://blog.graph.cool/thinking-in-terms-of-graphs-a9087423... https://dev-blog.apollodata.com/the-concepts-of-graphql-bc68... And a more full featured tutorial: https://www.howtographql.com/ Full disclosure - I'm the co-founder of Graphcool.
Comment linking /the-concepts-of-graphql-bc68bd819be3
on “Build Better GraphQL APIs: Thinking in Graphs”Submitted New Release of GraphQL Subscriptions for JavaScript as a story · 4 points
HN discussion
