What About the Database? How to Write Efficient Queries for GraphQL Resolvers (RYAN CHENKIE)

When writing GraphQL servers, we often place a lot of emphasis on how to craft good resolvers. However, we don't often think about how to create good database queries to furnish the data for those resolvers. Let's look at how it's easy to fall into the trap of writing inefficient database queries and how we can use GraphQL itself to solve this problem.
Resources:
Learn more about Summit - summit.graphql.com/
Explore the GraphQL FAQs - www.apollographql.com/docs/re...
Checkout the Apollo docs - www.apollographql.com/docs/

[@ehtishamali3564]

Great Explanation of Abstraction related stuff.

[@victorekpo7035]

Awesome info about the AST

[@ryanngalea]

Great info & talk from Chenkie as always, thankyou!

[@connoruriel6362]

Dont know if you guys gives a damn but if you're bored like me during the covid times then you can watch pretty much all of the new movies and series on Instaflixxer. Been streaming with my gf for the last months xD

[@haroldasher6494]

@Connor Uriel definitely, have been watching on Instaflixxer for since december myself :D

[@EduardoOviedoBlanco]

Nice presentation 👏

[@vorant94]

so... basically it means that we can just write one single global resolver to parse any GQL-query to SQL-query for a project of any scale (whether we have 1 table in database or 1000), doesn't it? It sounds weird... Not only we have one entry point for the whole API (the opposite of REST-full API), but even a resolver can be one for all?
P.S. I mean at least for getting data from a database, not mutating it

[@chologhuribangladesh7792]

what about deep nested query??

[@EduardoOviedoBlanco]

Please add the links to the video information.

[@trozzonick77]

Graphql should be used in very specific circumstances , replacing Rest with it is making just a dirty mess !