Keynote - JSON Graph: Reactive REST at Netflix

Why HN readers recommended it

HN commenters point to it as an alternative take on the data-fetching problem GraphQL addresses, and as a clear argument for when RPC or graph models beat plain REST.

This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.

Video & recommendation details

Creator / channel

Association for Computing Machinery (ACM)

Topic

api data fetching

Format

talk

Level

intermediate

HN recommenders in dataset

4

HN mentions in dataset

4

Recommendation years in dataset

2015–2023

These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.

From the original HN conversations

Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.

• I'm also excited to see Jafar Husain's Falcor: [VIDEO] It's a different implementation of the same concept.

• REST over HTTP is cache-able using CDNs like CloudFront. GraphQL isn't? If the client queries get too complex, processing GraphQL might take a toll on the server [0]. GraphQL completely makes sense for a client with limited processing power and battery life, but doesn't offer …

• > I had the impression RPC was seen as a mistake. For hypermedia/hypertext Fielding made a solid argument for preferring REST over RPC (mostly because of caching). I still recommend reading his very approachable thesis - these days not so much for the web/REST architecture, …