Hacker News new | ask | show | jobs
by jarcane 1707 days ago
I've begun to recognize "unnecessary GraphQL" as a code smell, and one usually indicative of wider architectural problems in a project.

I have yet to be wrong in immediately steeling myself for the worst the second I see the word.

1 comments

What would you consider to be "necessary GraphQL"
Nothing. But the utility it provides is a unification layer for heterogeneous data sources to enable ad-hoc queries on the consumer side.
Are you Facebook?
Pretty much this - I can see why Facebook use it but I wouldn't have gained much from GraphQL in any of my jobs.