4 ms·
GQL can return the top level query plus relations and any other entities needed for the view in response to a single request. The fact you don’t need separate r
by WiseWeasel 7y ago
GQL can return the top level query plus relations and any other entities needed for the view in response to a single request. The fact you don’t need separate requests or view-specific endpoints is significant.
- jacques_chester 7y agoRight, but if the answer to "it's too slow" and/or "it's too unpredictable" is "limit it to known queries", then ... how is that meaningfully different from known queries in SQL?
- ricardobeat 7y agoYou have control over what queries/entities get exposed in the graph. I think what he's saying is that most nested entities can be mapped to simple 'SELECT .. from .. where id = 1,2,3' queries, and a while a well-written JOIN might be more efficient, those have known performance and can benefit from caching, sharding etc.