Skip to content
Hallway
0:00 / 0:00

#falcor#jsongraph#netflix

Keynote - JSON Graph: Reactive REST at Netflix

Association for Computing Machinery (ACM)

49K subscribers • 7 videos on Hallway

YouTube
  • Recommended by 5 people: 4 on Hacker News and 1 on Lobsters.
  • A classic. People kept recommending it from 2015 to 2023.
  • Presented by Jafar Husain, Netflix
  • Linked in the descriptionPaper on dx.doi.org
  • May be out of date. Uploaded 11 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

40K views11 years ago5 recommendations

Web developmentSoftware designAPI designVue, Svelte, Angular and othersSoftware architecture

Jafar Husain explains Netflix's JSON Graph and Falcor, demonstrating how to model cloud data as a single virtual JSON object for client applications.

Every user of a web application wants to believe that all of the data in the cloud is sitting right on their device. Netflix's data platform "JSON Graph" creates this illusion for the web developer. One Model, Available Everywhere. Using an innovative combination of reactive programming techniques and RESTful principles, JSON Graph allows web developers to create a virtual server JSON model for their web application and transparently access it from any cloud-connected device. The Data is the API. Using JSON Graph, Netflix developers retrieve data from the virtual server model the same way they would from an in-memory JSON object. Efficient client/server interactions are ensured by batching concurrent idempotent requests, transparently optimizing requests into point queries, and caching recently-used data. Come learn about the innovative data platform the powers the Netflix UIs, and the new design patterns it enables. Jafar Husain dx.doi.org/10.1145/2742580.2742640

Why it's here

5 people recommend this

What people say. Recommended as a great explanation of Netflix's alternative to GraphQL, focusing on path-based data fetching and reactive REST principles.

ngrillyon Lobsters • Recommends

JSON Graph: Reactive REST at Netflix
5View on Lobsters

bsimpsonon Hacker News • Recommends

On “GraphQL Introduction”

I'm also excited to see Jafar Husain's Falcor: link to this video It's a different implementation of the same concept.
View on Hacker News

ignoramouson Hacker News • Recommends

On “RestCommander: Fast Parallel Async HTTP Client as a Service”

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 on the problem. Not sure what you mean by node.js "lacking backpressure"? Node.js is a very well suited solution to GraphQL, since GraphQL implies that the workload is going to to be IO bound. 0 link 0 link 1 link to this video
View on Hacker News

e12eon Hacker News • Recommends

On “Application Load Balancers enables gRPC workloads with end to end HTTP/2 support”

…ote procedure calls aren't inherently bad, but blurring the distinction too much between local procedure calls and remote ones aren't a great idea. From hung nfs mounts to unpredictable application performance, it is unpleasant. This Netflix talk on their not-graphql framework gives a very nice summary of when and how you might prefer RPC to REST: link to this video…
View on Hacker News

yencabulatoron Hacker News • Recommends

On “GraphQL vs. REST APIs: a complete guide”

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 be objects, so ` {from: 100, to: 200}` is a valid path segment, and this is how you build fancier query logic with in. link to this video
View on Hacker News