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

Questions

  1. What is the difference between str and String?
  2. Why can’t string slices be passed into a function (string slice meaning str as opposed to &str)?
  3. How do we access the data belonging to a key in a HashMap?
  4. When a function results in an error, can we handle other processes, or will the error crash the program instantly?
  5. Why does Rust only allow one mutable borrow at a point in time?
  6. When would we need to define two different lifetimes in a function?
  7. How can structs link to the same struct via one of their fields?
  8. How can we add extra functionality to a struct where the functionality can also be implemented by other structs?
  9. How do we allow a container or function to accept different data structures?
  10. What’s the quickest way to add a trait, such as Copy, to a struct?