dgs-framework VS async-graphql

I use DGS framework, it is a great open-source tool for writing graphql server api supported by Netflix.

The Netflix DGS would like to have a word with that claim lol.

I’ve never done open source work in my spare time. The only time I’ve contributed to an open source project was for an internship, so I’m not really sure that counts - the guidance was super strong.

I picked out an open source project I liked and found an issue I felt like I could do, and then hacked around until I solved it. I’m looking for advice for improvement be it hygiene, code style, communication style, anything. Help me grow as a soon to be entry level programmer.

https://github.com/Netflix/dgs-framework/pull/1248

Thanks.

Netflix's GQL: https://github.com/Netflix/dgs-framework

If you would like to try the DGS framework make sure to check out its official documentation and guides or jump straight into the DGS repo on GitHub.

I have found that the combination of [cargo lambda](https://github.com/cargo-lambda/cargo-lambda), [async graphql](https://github.com/async-graphql/async-graphql) and DynamoDB is an amazing combination for a backend stack, really cheap as lambdas are pretty minimal and insanely fast with the Rust runtime.

async-graphql

https://github.com/async-graphql/async-graphql maybe you need look this.

If you need more performance, don't use Node.js. async-graphql (Rust) or graphql-crystal (Crystal) will run circles around any Node.js server.

Who's using Async-graphql in production? · Issue #408 · async-graphql/async-graphql

Async-GraphQL Rocket integration

This post will discuss building a project management application with Rust using the Async-graphql library and MongoDB. At the end of this tutorial, we will learn how to create a GraphQL endpoint that supports reading and manipulating project management data and persisting our data using MongoDB. GitHub repository can be found here.