Defer execution of selection set to root resolver

[kevinmichaelchen]

What I currently have

I have a "bulk" mutation like the following:

mutation {
  createFoo(input: {id: 1}) {
    id
  }

  createBar(input: {id: 1}) {
    id
  }
}

According to the GraphQL spec, createFoo and createBar will be executed in sequence.

Each of these is handled by separate resolvers, each of which create separate database transactions behind the scenes.

What I'd like to see

Rather than separate transactions, I'd like one transaction.

This seems theoretically possible by deferring execution to the root resolver, which can "inspect" the selection set, determine which mutations the client would like to execute, and build one DB transaction.

Are there examples of how to do this?

I'm trying to build one here: https://github.com/kevinmichaelchen/go-gqlgen-deferred-execution-example

[kevinmichaelchen]

This kind of deferred aggregation seems possible with Data Loaders 🤔