> We knew how to avoid n+1's w/ SQL You can simply create one graphQL field corresponding to each REST end point you have now, and have it do an SQL query in t

> We knew how to avoid n+1's w/ SQL You can simply create one graphQL field corresponding to each REST end point you have now, and have it do an SQL query in the resolver. > you are adding an additional abstraction layer on top of your data store yes that is one of the main benefits (it allows you to coalesce data from multiple data stores).