I've created a tiny library which improves performance for GraphQL + Knex.
tl;dr
Before
After
- Filter
selectcolumns based on a query from clients - Load relations without N+1 problem (pagination available!)
https://github.com/acro5piano/knex-graphql-utils
Currently only PostgreSQL is supported, but I'll support other RDBMS too if needed.
Motivation
Creating a GraphQL service with a Relational Database is a hard thing. We should take care of:
- Performance for querying relations. N+1 problem will happen if you don't use Dataloader.
-
select *make your server slow, but hard to filter columns based on requests. - Pagination. Dataloader pattern is hard to implement pagination without a hacky
unionor window functions.knex-graphql-utilsusesrow_number()window function to do it.
As a developer, I noticed that I'm doing the same thing again and again - so I convert my work into a library.
The syntax is like this:
Please try it! Any feedback is welcome.
Oldest comments (1)
@acro5piano thanks for the write-up on this. I'm actively working on a NestJS/GraphQL/TypeORM project, and was looking into adding dataloader, and found this post... I didn't know about the pagination problem with dataloader, so I might hold off for certain resolvers for now. Anyway, just appreciate the info and the link to the github issue. If i were using knexjs, I would use your lib. Cheers!