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

Working with actors in Tokio

This will be the last time we rewrite our main.rs file. However, once we have finished this section, we will have built a basic actor model system. In our system, we will create an actor that keeps track of the orders so that we do not exceed our budget threshold. We then need to build an actor that sends the order, resulting in the following process:

Figure 14.5 – Our stock order interaction for actors

Figure 14.5 – Our stock order interaction for actors

We can see that this time round, we need to send the address of the actor that is making the order with the order message. This is a design choice because, in our system, order actors spin up and die quickly after the order has been made. We cannot keep track of the addresses for all the order actors in our program in our order book actor. Instead, the order book actor can get the address from the message to send the response to the order actor. First, we must import the following:

use tokio::sync::{mpsc, oneshot...