Re:PostGraphQL: PostgreSQL meets GraphQL
by untog on Monday December 12, 2016 @11:17PM
(#13164395)
Perhaps another way of asking it: how is GraphQL different to sending SQL statements from the client? In both scenarios you'd be "only" handling validation logic and ignoring the rest.
[ Parent
| on HN ]
Re:PostGraphQL: PostgreSQL meets GraphQL
by tscs37 on Tuesday December 13, 2016 @07:46AM
(#13166372)
Not much difference except that GraphQL does not specify how the data is processed.
You could answer the data out of a flatfile for all that the endpoint cares.
It also allows to secure access against arbitrary data requests, since on the server end, the resources only see the individual requests to the DB.
In my experience, it's much easier and less verbose to validate GraphQL after parsing than just validating any SQL you plan to pass to the backend.