@DMehaffy in which way a query performed with graphql is to be considered performance optimised compared to a REST one, if the same controller is in place?
Please pardon such a naive question. While defining what fields do I actually want in my frontend is surely to be more performant in terms of transport overhead, though it is still unclear for me, how the actual db query is affected.
There is an example: let’s say in a find() controller action I’m accessing all fields from a related entity, to make some sort of an aggregation. Now in a graphql query I’d like to get only related entity’s id. In my understanding no optimisation in querying a db will take place here.
Could you please elaborate on Strapi’s query optimisation mechanism, which takes place when graphql is in use – I could not find any insights on this one.
Thank you!
UPD: my concerns are briefly described here and related issues