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
Part 1:Getting Started with Rust Web Development
Part 2:Processing Data and Managing Displays
Part 3:Data Persistence
Part 4:Testing and Deployment
Part 5:Making Our Projects Flexible
Part 6:Exploring Protocol Programming and Async Concepts with Low-Level Network Applications


  1. We create an actor that has a minimum of two fields. These two fields hold the sender for the channel of the actor we are sending messages to and the receiver of the channel we are receiving messages from. Then, we need a run function to enable our actor to run awaiting incoming messages.
  2. If we do not create a thread to run our long-running actors, our main runtime will be blocked by this actor running. If only one actor is running after the server is listening, this is OK; however, if there are multiple actors or a loop that is accepting TCP traffic, then we have a problem as the system will essentially be gridlocked and our actor system will not work.
  3. We can build an actor that essentially acts like a router. It can keep track of incoming messages and alternate sending messages to multiple different actors who do the same type of job. However, do not do this if multiple actors rely on the internal state.