Cost can be the number or variety of components needed to resolve a field. Other considerations are avoiding N+1 query patterns.

We have key fields that talk to Cassandra and Redis and a smattering of other web services.

sure, that part I understand. I’m thinking more along the lines of somthing like resolve-person-by-name, resolve-person-by-city-- those could be handled by the same resolver that looks at the query arguments, or handled by separate resolvers

or, of course, created by a def-resolver macro that straddles the line between common code and individual functions per resolver