Netflix’s Falcor makes Data Fetching as Simple as Simple Can Be

By | 2015-10-10

Netflix’s Falcor Handles Data Transport and Caching From Source to Destination

Falcor gives you a model you can treat as a reliable, in-memory local cache of remote data. All the heavy-lifting is done for you. The mechanics of retrieving, caching, batching requests, and removing duplicate requests between client caches and server databases is done without mess that would happen were you to try to build it all yourself.

Data is accessed from a Falcor Model: the Falcor Model can be considered a wrapper around your JavaScript data model objects. You must get a value via the Falcor Model, using the JavaScript (dot) path (e.g. ‘user.firstname’) in your data model.

The API consists of three commands: “get”, “set”, and “call”.

The API is asynchronous, which means when the values are ready, whether drawn from local cache or remotely, will be passed to the client’s callback function.

The client of the Falcor Model gets efficient data fetching where the data is the API. But there is a bit of upfront work involving Routing and JSON Graph development that makes the system work so well. More on that later…


Leave a Reply

Your email address will not be published. Required fields are marked *