- Really straight forward, easy to learn
- Things like caching and query-merging included
- Not as powerful as GraphQL (no arguments)
- No built-in model/schema introspection
- Very powerful and flexible
- Static types and introspection — GraphiQL FTW
- Many implementations in other languages, growing community
- Steeper learning curve
- No batteries included. Fair amount of assembling required
- FalcorJS and GraphQL are tackling the same problem (querying data, managing data).
- The important distinction is that GraphQL is a query language and FalcorJS is not.
- When you are asking FalcorJS for resources, you are very explicitly asking for finite series of values. FalcorJS does support things like ranges, e.g.
genres[0..10]. But it does not support open-ended queries, e.g.
- GraphQL is set based: give me all records where true, order by this, etc. In this sense, GraphQL query language is more powerful than FalcorJS.
- With GraphQL you have a powerful query language, but you have to interpret that query language on the server.