Book Image

Rust Web Programming - Second Edition

By : Maxwell Flitton
Book Image

Rust Web Programming - Second Edition

By: Maxwell Flitton

Overview of this book

Are safety and high performance a big concern for you while developing web applications? With this practical Rust book, you’ll discover how you can implement Rust on the web to achieve the desired performance and security as you learn techniques and tooling to build fully operational web apps. In this second edition, you’ll get hands-on with implementing emerging Rust web frameworks, including Actix, Rocket, and Hyper. It also features HTTPS configuration on AWS when deploying a web application and introduces you to Terraform for automating the building of web infrastructure on AWS. What’s more, this edition also covers advanced async topics. Built on the Tokio async runtime, this explores TCP and framing, implementing async systems with the actor framework, and queuing tasks on Redis to be consumed by a number of worker nodes. Finally, you’ll go over best practices for packaging Rust servers in distroless Rust Docker images with database drivers, so your servers are a total size of 50Mb each. By the end of this book, you’ll have confidence in your skills to build robust, functional, and scalable web applications from scratch.
Table of Contents (27 chapters)
Free Chapter
1
Part 1:Getting Started with Rust Web Development
4
Part 2:Processing Data and Managing Displays
8
Part 3:Data Persistence
12
Part 4:Testing and Deployment
16
Part 5:Making Our Projects Flexible
19
Part 6:Exploring Protocol Programming and Async Concepts with Low-Level Network Applications

Answers

  1. Rust’s strong typing system will complain. This is because async blocks behave like closures meaning that every async block is its own type. Pointing to multiple futures is like pointing to multiple types, and thus it will look like we are returning multiple different types.
  2. We add a new module in the views directory with the new views. These have the same endpoints and views with new parameters that are needed. We can then add a version parameter in the factory function. These new views will have the same endpoints with v2 in them. This enables users to use the new and old API endpoints. We then notify users when the old version will no longer be supported, giving them time to update. At a specific time, we will move our version in the build to v2, cutting all requests that make v1 calls and responding with a helpful message that v1 is no longer supported. For this transition to work, we will have to update the allowed versions in the build config to a list...