4 ms·
(Author here) If you want efficient database JOINs using GraphQL I'd always opt for Hasura. They've done a fantastic job solving this problem. This will almost
by jensneuse 6y ago
(Author here) If you want efficient database JOINs using GraphQL I'd always opt for Hasura. They've done a fantastic job solving this problem. This will almost always use the most efficient SQL you can get. If you want to extend this Schema you can use something like Schema stitching and you're good to go.
- golergka 6y agoThat's exactly what I'm using though! And for the most part, it's an awesome tool. But it still can't magically make resulting SQL query faster than it can be without tweaking the database itself.
- aszen 6y agoWill hasura also help with the indexes, the most efficient SQL is usually the one which utilizes the indexes properly which still need to be setup to accomodate for each and every client side queries. Besides hasura would have been great as a library but it's another api server you need to maintain on top of your existing one.
- jensneuse 6y agoI think it would be a nice feature @tanmaigo should add to Hasura if it's not alredy there. Hasura could automatically detect slow queries and suggest indexes.
- wayneftw 6y agoOh boy so now I have to set up and maintain a Hasura instance Instead of writing a simple SQL query? Sounds like a dream!