aws-sdk-rust VS sea-query

> What kind of plans for support of Rust's evolving async ecosystem?

We were hoping async-function-in-trait would land before GA, however, we have a plan to add support in a backwards compatible way when it's released.

> Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps?

Our roadmap has unfortunately been in a state of disrepair for some time. We're hoping to get it cleaned up and accurate post GA.

> Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically AWS SDKs have been inconsistent on. Just a request not really a question :-)

There are lots of examples here [1], some simple, some quite complex. If there's something you have in mind, please file an issue! Having great examples is one of our priorities.

[1]: https://github.com/awslabs/aws-sdk-rust/tree/main/examples

Yep! There are actually examples that use Web Assembly: https://github.com/awslabs/aws-sdk-rust/tree/main/examples/w...

i'm using https://github.com/awslabs/aws-sdk-rust heavily and was wondering if there was a more specific community (subreddit, Discord server, etc) of Rust x AWS developers?

Only relevant search result was this github issue, which didn't really solve the problem.

I went on rusoto just because aws-sdk-rust says at the beginning of the readme:

Official libraries for major cloud vendors will definitely boost Rust's adoption. aws-sdk-rust is still in 'developer preview', but it's getting there.

rusoto replaced by aws-sdk-rust to interface with AWS services for storage (S3), background jobs (SQS) and sending emails (SES).

For AWS, there is both the new official SDK preview (https://github.com/awslabs/aws-sdk-rust), and the older unofficial one (https://github.com/rusoto/rusoto). I've not used the new one, but rusoto was excellent when I used it a few years ago.

The main limitation of prepared statement is that you can only insert values, so you cannot dynamically construct the query depending on the parameters. For that, you can use a query builder such as sea-query, which should handle that.

🎉 We are pleased to release SeaQuery 0.27.0! Here are some feature highlights 🌟:

SeaORM or SeaQuery are also very good instead of diesel/sqlx

SeaQL.org was founded back in 2020. We devoted ourselves into developing open source libraries that help Rust developers to build data intensive applications. In the past two years, we published and maintained four open source libraries: SeaQuery, SeaSchema, SeaORM and StarfishQL. Each library is designed to fill a niche in the Rust ecosystem, and they are made to play well with other Rust libraries.

Upgrade sea-query to 0.26

As the new member of the SeaQL family, it's a stellar example of what could be done with Rust and the SeaORM / SeaQuery / SeaSchema suite of tools. We couldn't be more excited to see applications being built on Rust and the SeaQL ecosystem!

The first piece of tool we released is SeaQuery, a query builder with a fluent API. It has a simplified AST that reflects SQL syntax. It frees you from stitching strings together in case you needed to construct SQL dynamically and safely, with the advantages of Rust typings.

Built upon SeaQuery, SeaORM allows you to build complex queries without 'fighting the ORM'.

I wrote a first bridge for sea-query to diesel https://github.com/SeaQL/sea-query/discussions/168. With the indications of /u/weiznich I think I can make it better and probably it's own crate. Maybe even reduce the boilerplate by generating the Iden directly from the diesel schema.

Related Issue & PR - https://github.com/SeaQL/sea-orm/issues/499 - https://github.com/SeaQL/sea-query/pull/256