5 ms·

sorry for stupid question, how REST and database indexes are related?

• diveanon 6y ago
  They aren't. There is just a lot of anti-patterns floating around because of tightly coupled API / DB's. People apply this same logic to GQL and get confused.
  • cratermoon 6y ago
    > People apply this same logic to GQL And programmers will apply this same anti-pattern to GQL, so it doesn't really solve that problem, and arguably makes it worse for the reasons stated in the un-indexed field example.
    • diveanon 6y ago
      And that is why you used gql codegen and typing to limit their capability to do so. Part of the benefit of gql that people often overlook is its self documenting nature and when tied with automation tools its ability to provide a lot of flexibility for developers without compromising you db. The gql server is ultimately what is responsible for this, and we use schema introspection to ensure the searchable / sortable fields are only exposed if indexed.
      • cratermoon 6y ago
        Should I go back into my archives and look over the number of technologies leaning on code generation and model introspection that failed to catch on?
• cs-szazz 6y ago
  They're not really related here. The premise of my question is more around the fact that with REST, which database queries you'll run are fairly static and are known by the backend based on what APIs they expose. Therefore it's easy (ish) to make sure said queries are indexed properly. With GraphQL, I'm asking about how clients _could_ write arbitrary requests, that since the backend doesn't know about them ahead of time, can't optimize for with indexes.
  • sysashi 6y ago
    That makes sense, thanks!