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 can serve HTML data by merely defining a string of HTML and putting it in the body of an HttpResponse struct while defining the content type as HTML. The HttpResponse struct is then returned to the user’s browser.
  2. The simplest way is to hardcode a full HTML string with the CSS hardcoded in the <style> section, and our JavaScript hardcoded in the <script> section. This string is then put in the body of an HttpResponse struct and returned to the user’s browser.
  3. We make a CSS file that defines the components that we want to be consistent throughout the app. Then, we put a tag in the <style> section of all our HTML files. Then, with each file, we load the base CSS file and replace the tag with the CSS data.
  4. After the API call, we must wait for the status to be ready. Then, we get the HTML section we want to update using getElementById, serialize the response data, and then set the inner HTML of the element as the response data...