4 ms·
I'm not sure why author dismisses graphql. It greatly simplifies server-side work. You just need to implement one endpoint that responds accurately and quickly
by scotty79 11y ago
I'm not sure why author dismisses graphql. It greatly simplifies server-side work. You just need to implement one endpoint that responds accurately and quickly to a composed query in accordance to what rights the current user has. It's not as easy as "serve result of SELECT *" but it's well defined and flexible for consumers.
- c17r 11y agoAgree. His opening complaint is from the Front End saying "I need x, y, and z so make me an API that returns {x, y, z}" which he wouldn't need to do for them if they were using GraphQL.
- weq 11y agoIQueryable. Go look it up. MS did GraphQL years ago. If you got out of your insurlar JS/FB/Twitter bubble, u will see the anti-pattern that IQueryable become.
- scotty79 11y agoI don't think IQueryable is very composable. It goes bit beyond simple query builder because it can automatically translate for you more expressive queries into SQL (http://www.infoq.com/presentations/theory-language-integrated-query http://www.infoq.com/presentations/theory-language-integrate... ) But I don't think people could define parts of IQueryable in .ascx files and compose it into single IQueryable result of which feeds the components. That's the main idea of graphql.
- hokkos 11y agoGraphQL is "structurally typed" where IQueryable is nominally typed by its generic argument. This make GraphQL more easily composable, but IQueryable is still composable with functions.
- keithwhor 11y agoIt can be as easy as "serve result of SELECT *". We're working on it with Nodal. http://graphql.nodaljs.com/ http://graphql.nodaljs.com/ - some pretty neat progress so far.