Rusoto codegen, part two
In the previous post we took a quick tour of the major pieces of Rusoto code generation. In this post we’ll get deeper into code generation for the Simple Queue Service. Picking up from part one Part one described a few parts of Rusoto codegen: Finding which services to generate Making the service’s crate Generating the service and placing it inside its crate rustfmt the generated code to make it look pretty Step three is where this post will concentrate.
Rusoto codegen
Writing a software development kit (SDK) is a challenge. Especially when the target has a tremendous number of services, endpoints and different styles of interacting, such as REST, querystring and “other.” Rusoto uses the botocore service definitions to create Rust code to interact with Amazon Web Services. Let’s dive into how it’s done! Using Simple Queue Service as an example To make this post clearer, we’ll follow the Simple Queue Service (SQS) from botocore service definition to the rusoto_sqs crate.
Rusoto RDS walkthrough, mk 2
Since the publication of Rusoto RDS walkthrough, a new version of Rusoto has been released: 0.25.0. This includes some breaking changes so let’s work through those. We’ll also be cleaning up some of the rougher edges in the previous walkthrough. rusoto-rds-mk2 The previous project’s source code is on github. We’ll be making a new project based off that one. You can see the final product in rusoto-rds-mk2 folder. Cargo.toml changes required for Rusoto 0.
Rusoto RDS walkthrough
Let’s tie some great Rust crates together! In this walkthrough, we’ll use Rusoto to create a Postgres RDS database instance, Rocket.rs to make a web server and Diesel to talk to the database on AWS to make a proof of concept hit counter. Walkthrough overview There are two projects in this walkthrough. First is rusoto-rds. This creates the Amazon Web Services (AWS) Relational Database Service (RDS) instance and should be run first.