juniper VS async-stream

juniper

GraphQL is also an option. https://github.com/graphql-rust/juniper

Juniper has plenty of popularity, so I guess it's Rust + graph DB that doesn't get much love then... :/

rusty-gql would not be able to release without async-graphql and juniper.

I'm looking for graphql server that can do queries and mutations over websocket, like subscriptions-transport-ws. Juniper and async-graphql both looks promising and async-graphql at least uses wording Subscriptions (WebSocket transport) in features but i couldn't find much more or any examples about that from the docs or repo.

We also don’t use Node anymore. We found Node in general to be incredibly slow, not to mention single threaded. Admittedly, we did use Node (Apollo) though up until about two years ago. Now, depending on use-case, we will use Go (https://github.com/99designs/gqlgen) or Rust (https://github.com/graphql-rust/juniper). Both outperform a Node gateway but significant margins.

(example from the docs async-graphql https://async-graphql.github.io/async-graphql/en/subscription.html, juniper: https://github.com/graphql-rust/juniper/blob/master/docs/book/content/advanced/subscriptions.md)

I might even start smaller than that, and try creating a basic function using async-stream's stream! macro that just yields an incrementing i64 and return that from within a subscription, to get an idea for how it works.