Falcor vs GraphQL?

Falcor Pros:

  • Really straight forward, easy to learn
  • Things like caching and query-merging included

Falcor Cons:

  • Not as powerful as GraphQL (no arguments)
  • No built-in model/schema introspection
  • No implementations other than JavaScript, and little visible traction

GraphQL Pros:

  • Very powerful and flexible
  • Static types and introspection — GraphiQL FTW
  • Many implementations in other languages, growing community

GraphQL Cons:

  • Steeper learning curve
  • No batteries included. Fair amount of assembling required
  • Relay (Javascript GraphQL client) has a steep learning curve

ref: https://dev-blog.apollodata.com/graphql-vs-falcor-4f1e9cbf7504#.oc1r34ea3

  • 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. genres[0..*].
  • 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.

ref: http://stackoverflow.com/questions/32057785/what-is-the-difference-between-falcor-and-graphql



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s