@samnewman I was reading your post about BFF and wondering if that's a problem solved by GraphQL. cc @lplotni
-
-
Theoretically maybe. The devil is in the detail. Which flavour of graphQL for example? And you still have to implement the "query" execution
3 replies 0 retweets 0 likes -
Replying to @samnewman @lplotni
Hum... cookies n cream? :-) jk aside, it's just a hypothetical question. Since it allows diff clients to get data differently.
3 replies 0 retweets 0 likes -
My point is that vanilla GraphQL has a bunch of gaps, and just defines the language, not the implementation
1 reply 0 retweets 0 likes -
Replying to @samnewman @lplotni
Can you point me anywhere where I can read more on your considerations about GraphQL limitations?
1 reply 0 retweets 0 likes -
@southpolesteve outlined a bunch in his talk here: http://ndcoslo.com/talk/going-serverless-with-graphql/ …2 replies 0 retweets 0 likes
We went through a lot of pain before realizing dataloader+relay spec were pretty critical to making a good production graphQL api
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.