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. The actor model is where actors send messages to each other. Each actor has a queue for processing the incoming messages for the actor. Because of this, the incoming messages are processed in the order they are received.
  2. The actor receiving the initial message has the receiver of the MPSC channel. The actor sending the initial message has the sender for the MPSC channel and creates a one-shot channel. The actor sending the initial message then sends the sender from the one-shot channel in the initial message. The actor sending the initial message then waits for the actor receiving the initial message to process the data and then uses the sender in the initial sender to send back a response.
  3. Our program will run as we expect; however, only two of the senders for the MSPC channel will be killed as we only have two actors that are sending messages. This means that one sender will be left over. As one sender is not used up, the channel is not closed, so the receiving...