4 ms·
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 l
by jarym 3y 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/ https://netflix.github.io/falcor/
- lfkdev 3y ago`Sad Prime noises`
- dustingetz 3y agoiirc falcor predated graphql
- ppseafield 3y agoI was at the React Rally conference where Falcon was publcly announced in August of 2015. I recall that Facebook gave a GraphQL presentation right before. It seems GraphQL was first announced publicly in February 2015.
- parthdesai 3y agoNetflix themselves have moved off falcor though https://netflixtechblog.com/migrating-netflix-to-graphql-safely-8e1e4d4f1e72 https://netflixtechblog.com/migrating-netflix-to-graphql-saf...
- deleted 3y ago[deleted]
- paulbakker 3y agoFalcor is actually part of the "old" architecture described in the talk. Because it's mostly unknown and no longer used I didn't go into the details of it. Falcor was developed at the time Facebook was developing GraphQL in-house. It has similar concepts, but never took off the way GraphQL did.
- baby 3y agoProbably because most people don't want to work with Java