4 ms·
I've watched Jafar talk about Falcor. Didn't know about it before since GraphQL is so dominant in the space. If you're just getting into these, the major diffe
by avitzurel 10y ago
I've watched Jafar talk about Falcor. Didn't know about it before since GraphQL is so dominant in the space.
If you're just getting into these, the major difference is the verbosity and the learning curve.
With GraphQL you need to know a lot about the schema and the types (which can be a good thing as well), with Falcor you don't and there's no easy way to code types (at least that I know of).
Whatever you choose though, I do encourage you to choose one. I have seen many APIs fail on performance because they send too much data down the wire just because one of the consumer needs it.
- benjaminjosephw 10y agoSending redundant data feels wrong but responses can (sometimes) be cached and messages compressed. I thought that the main advantages to Falcor or GraphQL was around reducing network calls and querying multiple data sources from one endpoint. If the same type and structure of data is requested with only variations in which fields consumers are actually using, isn't traditional REST still a good/better fit?
- yen223 10y agoTo me, the biggest benefit of adopting GraphQL was its strong-type system, which made communicating API specs between the client and server much more transparent The reduction in network calls is an incidental bonus - most of the time you won't see it.