Hacker News Reader

It's bad to write SQL queries on the client side :-)

Exactly. That's why we needed a new tool that does exactly the same thing, but allows us to say we're doing something different. </s>

I have always had the impression that graphql was built for a problem Facebook has, but that most of the rest of us don't (numerous complex backend (some non-SQL) data sources and highly independent frontend teams moving very quickly).

As I work in an environment where there are no frontend vs backend developers, and we have a single SQL database, graphql is a neat tool which solves some problems I will probably never have.

Well I use graphql to get data stored in Redis, ElasticSearch or is just calculated on the fly. It’s just an api endpoint.

Is it?

Or is it just bad to pass unsanitized SQL queries? Because that’s the only issue I think. GraphQL seems effectively an input data sanitizer.

Reply on news.ycombinator.com