Comment by no_wizard

4 days ago

GraphQL says nothing about databases at all. Resolvers can get resources from anything, they’re agnostic.

None of that is inherent to the technology but it’s a common folly among developers. This is an issue with REST too but it can be more obfuscated

4 comments

no_wizard

Reply
ITB  4 days ago

If a certain arrangement makes it more likely to write bad queries, and it requires extra care to write optimal queries, then it’s a worse interface to a database. I bet for really database intensive applications graphQL adds more work than it saves.

  • no_wizard  4 days ago

    It’s not though. Especially since GraphQL makes no mention of databases. It’s a resource agnostic protocol.

    This isn’t a technical issue with GraphQL. It’s a culture issue among developers who shoehorn GraphQL and don’t use it appropriately

    As someone who works on very database intense application GraphQL saves me more work than its ever caused.