nexus-repository-cargo VS juniper

I'm primarily a Go developer, and for that we use Sonatype Nexus to cache dependencies online, and we sync those offline to pull from. That works pretty well for us, and we use this for a bunch of languages like Ruby, C#, NodeJS, etc. But it looks like Nexus doesn't support Cargo, and the only community plugin I could find only supports hosting, while I need a proxy. I did see Artifcatory has some level of Cargo support, but we have to have an open-source solution. We also mirror the Ubuntu repositories, so we get our C/C++ libraries through that. I've noticed Rust dependencies in there, but they don't work through Cargo from what I've seen.

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)