JsonAPI VS Falcor

In addition to saving you time on boilerplate, the API provided by Hatchify fully implements the JSON: API specification, which stipulates solid standards to define the peculiarities of CRUD REST APIs. Get back all the time spent bike-shedding how to implement standard API features like filtering, pagination, including related data, etc. JSON: API offers consistent practices for frontend and backend developers to... - Source: dev.to / about 2 months ago

-JSON:API format responses (https://jsonapi.org) for better standardization. Built using Ruby on Rails, Sunnybox is designed to offer a powerful yet easy-to-use solution for developers managing email systems. I'd really appreciate your feedback on: - The API's user-friendliness and efficiency. - Source: Hacker News / 5 months ago

As we’re building a RESTful API that’s formatted by the JSON:API specification and store our data in a MySQL8 relational database, a few things were pretty straightforward – we need a new model and we’ll name it Custom Field (naming wasn’t an issue here 🥲). - Source: dev.to / 5 months ago

I found json api spec[1] recently. This kind of is better standard for REST APIs. It is bit rough to handle client side but once you get the hang of it, it is breeze to use [1] https://jsonapi.org/. - Source: Hacker News / 6 months ago

That's it! Now we have a complete set of RESTful CRUD APIs at "/api/zen" that conforms to the JSON:API specification, and the access policies fully protect the APIs. The API provides rich filtering and relation-fetching capabilities. The following are some examples; you can find more details here. - Source: dev.to / 8 months ago

Interesting the article jumps straight from REST to GraphQL and forgets Falcor[0] - Netflix's alternative vision for federated services. For a while it looked like it might be a contender to GraphQL but it never really seemed to take off despite being simpler to adopt. [0] https://netflix.github.io/falcor/. - Source: Hacker News / 7 months ago

- obviously netflix with falcor, EVCache and hundreds of other projects. Source: almost 2 years ago

I pushed for Falcor over GraphQL in 2016. I still think Falcor was a more elegant core idea, but the implementation, tooling, and community never materialized like it did with GraphQL, and now Falcor is relatively niche and obscure. Netflix wasn't willing or able to promote it like Facebook did with GraphQL. That was beginning to be apparent in 2016, but I liked the concept too much. Source: over 2 years ago

Netflix has two amazing aspects I think. One is obviously the movie infrastructure and the other the way they do data and state management. I would read up on https://netflix.github.io/falcor to get an idea what is involved here.to be honest I dont get the point of rebuilding the visual aspects of their web app, that part is trivial and also completely useless without the parts that matter. Source: almost 3 years ago