3 ms·
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
by jarcane 5y 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.
- corpdronejuly 5y agoWhat would you consider to be "necessary GraphQL"
- jarcane 5y agoAre you Facebook?
- jamesfinlayson 5y agoPretty much this - I can see why Facebook use it but I wouldn't have gained much from GraphQL in any of my jobs.
- dgb23 5y agoNothing. But the utility it provides is a unification layer for heterogeneous data sources to enable ad-hoc queries on the consumer side.