You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@clifinger did you know about async-graphql
At this moment this solution has more features and I feel better then use of jupiter.
I personally followed the implementation of twentyfive-stars and liked the interface more than Jupiter. Jupiter supports async, but not released yet and Jupiter lack of good documentation when async-graphql has excellent book
During the investigation, I came across sqlx and found this native rust driver feature to verify SQL during the build is awesome and helps to find bugs before the actual run.
I have tried all 3 and finally stopped on sqlx, diesel is crazy complex and not native driver, tokio-postgres is too basic and sqlx is a very good balanced generic solution and I feel performance would be better as it does not have a dependency on libpq (C driver)
I think, that for Bollerplate we need to pick the best solutions on the market and diesel and Jupiter are not the best
The text was updated successfully, but these errors were encountered:
olexiyb
changed the title
discussion: async-graphql vs jupiter and diesel vs tokio-postgres
discussion: async-graphql vs jupiter and diesel vs tokio-postgres vs sqlx
Jun 29, 2020
async-graphql appears to have more features but many of them do not belong in a library and push async-graphql into framework territory. Juniper is firmly in the library camp. It's mainly preference and what you are looking for. The GraphQL featurset is the same for both (minus interfaces on Juniper master, which we are revamping). If there are missing GraphQL features, please file tasks on Juniper!
@clifinger did you know about async-graphql
At this moment this solution has more features and I feel better then use of jupiter.
I personally followed the implementation of twentyfive-stars and liked the interface more than Jupiter. Jupiter supports async, but not released yet and Jupiter lack of good documentation when async-graphql has excellent book
During the investigation, I came across sqlx and found this native rust driver feature to verify SQL during the build is awesome and helps to find bugs before the actual run.
There are actually 3 choices:
I have tried all 3 and finally stopped on sqlx, diesel is crazy complex and not native driver, tokio-postgres is too basic and sqlx is a very good balanced generic solution and I feel performance would be better as it does not have a dependency on libpq (C driver)
I think, that for Bollerplate we need to pick the best solutions on the market and diesel and Jupiter are not the best
The text was updated successfully, but these errors were encountered: