GraphQL Is a Trap?

Re:GraphQL Is a Trap? by camgunz on Friday May 06, 2022 @04:35PM (#31289379)

I think GraphQL is best understood as an incomplete ORM that you have to complete yourself on the backend. If GraphQL generated SQL (given some tooling or what have you) pretty much all the problems are solved. Indeed backend-as-a-service products like Hasura or Postgraphile are this missing piece. I guess we're uncomfortable with SQL over the wire or open-to-the-world databases, but we shouldn't be.

Or maybe TLDR "dear next generation of engineers: SQL is actually pretty good".

[ Parent | on HN ]

Re:GraphQL Is a Trap? by discreteevent on Friday May 06, 2022 @04:41PM (#31289427)

SQL is excellent but exposing your database is not. The inventors of graphql specifically said that they don't think that it is a good idea to do so. They never intended it for that.

[ Parent | on HN ]

Re:GraphQL Is a Trap? by camgunz on Saturday May 07, 2022 @01:56PM (#31296886)

> SQL is excellent but exposing your database is not.

That was definitely true before Postgres got row security (admittedly in 2016, after GraphQL was released in 2015), but these days there's really no need to run an entire app server in front of your database just to implement permissions.

[ Parent | on HN ]