I’ve found that articulating my disdain for classical object-oriented inheritance models after a decade of experience does not sit well with the typical interviewer, whose questions seem to come from the top three links of a Google search.
Dan Abramov is more conciliatory in How to Use Classes and Sleep at Night. He basically provides rules on how to minimize misuse of the ES6 class.
(To clarify, the only great, maintainable use-case I’ve found for the OO hierarchy is for application life-cycle support.)
Part 1: How to Escape the 7th Circle of Hell
Disclaimer: GraphQL is still new and best practices are still emerging. This post describes some of my journey with impl…
Source: From REST to GraphQL — Medium
In this article, Jim Webber, Savas Parastatidis and Ian Robinson show how to drive an application’s flow through the use of hypermedia in a RESTful application, using the well-known example from Gregor Hohpe’s “Starbucks does not use Two-Phase-Commit” to illustrate how the Web’s concepts can be used for integration purposes.
Source: How to GET a Cup of Coffee
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.
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…