Keynote - JSON Graph: Reactive REST at Netflix

Channel:Association for Computing Machinery (ACM) · Length:54:57 · Published:2015-04-01 · Views:40925

Watch on YouTube

Summary

Jafar Husain's ACM keynote presents Netflix's JSON Graph and Falcor, which let web developers treat all cloud data as one virtual JSON model. It combines reactive programming with REST principles.

Why HN recommends 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.

gives a very nice summary of when and how you might prefer RPC to REST — HN, 2020

Web development · Software architecture & design

Subtitles (excerpt)

Uh so I'll just introduce our keynote speaker for the morning who's Jafar Hussein who's going to talk to us today about some work done at Netflix. Short and sweet. All right. Hi everybody. Uh welcome to my talk. Uh it's called Falor. Uh I'm from Netflix. Um so I mean really I think the the theme behind this presentation is that I think most users really want to believe the entire cloud is sitting right there on their device. And so Falor is a project that we came up with at Netflix and what our conception was was really that we wanted to be able to code that way as developers. We wanted to be able to basically imagine that all the data on the cloud was sitting right there on the device. Now there are lots of frameworks to try and do this. Um but really over the last three years we've kind of radically reimagined the way that clients talk to the server and we think it's you know it's definitely um unique if not innovative certainly a a com combination of things that hasn't necessarily been done in this particular way before. And so we're I'm interested to talk to you guys about it. Um, a little bit about myself. I'm Netflix's cross team technical lead. Uh, I am the architect of Falcore and I'm active participant in the TC39.

On Hacker News

It hasn't seen much outside adoption, you might enjoy the ideas behind Netflix's Falcor: [LINK] You can think of it as larger-than-what's-downloaded dynamically-generated JSON object with internal pointers where you can ask to access wanted paths. (Sort of like GraphQL is a larger-than-what's-downloaded dynamically-generated non-JSON object.) One trick they use is that the path segments can also … — yencabulator, 2023-03
> 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, but for the other ones, which include modern SPAs (they're not great as hypermedia apps, but fine as networked applications)… — e12e, 2020-10
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 a great deal in terms of server-to-server communication. JSON Graph by Netflix [1] is worth a look-in for a different take… — ignoramous, 2016-04
I'm also excited to see Jafar Husain's Falcor: [VIDEO] It's a different implementation of the same concept. — bsimpson, 2015-05

Related videos