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

Running it all in Docker

We are now at the stage where we can run our entire application in Docker. This enables us to have multiple workers pulling from the same Redis queue. First, we need to define the Dockerfile for the build of our worker/server image. We are going to have a distroless build for the Docker build with the following code:

FROM rust:1.62.1 as build
COPY . .
cargo build --release 
COPY --from=build /app/target/release/task_queue 
ENTRYPOINT ["task_queue"]

This distroless build should not be a surprise at this point in the book. We are merely compiling the application and then copying the static binary into the distroless image. Before we run the build in any way, we must ensure that we do not copy over excessive files from the target directory into our Docker build with the following code in the .dockerignore file: