The dark side of GraphQL: performance

Re:The dark side of GraphQL: performance by picardo on Wednesday January 01, 2020 @05:50PM (#21931301)

I never used Absinthe, but if you're initializing an ORM in your resolver, loading the entire record into memory is unavoidable. How does Absinthe get around that? (Sounds like it generates the SQL?)

[ Parent | on HN ]

Re:The dark side of GraphQL: performance by nivertech on Thursday January 02, 2020 @02:54PM (#21939093)

Absinthe does some dumb things by default too. You need to manually optimize your resolvers.

One annoying thing Absinthe did by default I noticed was fetching entire object from DB, even though the GraphQL query only returns it's ID. For example query below would fetch each person from a DB, even though we already had a list of person IDs on the friends level:

  {
    friends {
      person {
        id
      }
    }
  }

[ Parent | on HN ]

Re:The dark side of GraphQL: performance by sergiotapia on Wednesday January 01, 2020 @06:39PM (#21931626)

you point it to a resolver, in your resolver your resolve, in other words write the query

[ Parent | on HN ]