Book Image

Rust Web Programming

By : Maxwell Flitton
Book Image

Rust Web Programming

By: Maxwell Flitton

Overview of this book

Are safety and high performance a big concern for you while developing web applications? While most programming languages have a safety or speed trade-off, Rust provides memory safety without using a garbage collector. This means that with its low memory footprint, you can build high-performance and secure web apps with relative ease. This book will take you through each stage of the web development process, showing you how to combine Rust and modern web development principles to build supercharged web apps. You'll start with an introduction to Rust and understand how to avoid common pitfalls when migrating from traditional dynamic programming languages. The book will show you how to structure Rust code for a project that spans multiple pages and modules. Next, you'll explore the Actix Web framework and get a basic web server up and running. As you advance, you'll learn how to process JSON requests and display data from the web app via HTML, CSS, and JavaScript. You'll also be able to persist data and create RESTful services in Rust. Later, you'll build an automated deployment process for the app on an AWS EC2 instance and Docker Hub. Finally, you'll play around with some popular web frameworks in Rust and compare them. By the end of this Rust book, you'll be able to confidently create scalable and fast web applications with Rust.
Table of Contents (19 chapters)
1
Section 1:Setting Up the Web App Structure
4
Section 2:Processing Data and Managing Displays
8
Section 3:Data Persistence
12
Section 4:Testing and Deployment

Questions

  1. Why can we not simply code multiple futures into the middleware and merely call and return the one that is right, considering request parameters and authorization outcomes, but instead have to wrap them in an enum?
  2. How do we add a new version of views but still support the old views if our API is serving mobile apps and third parties that might not update instantly?
  3. Why is the stateless constraint becoming more important in the era of elastic cloud computing?
  4. How could we enable another service to be incorporated utilizing the properties of the JWT?
  5. A warning log message hides the fact that an error has happened from the user, but still alerts us to fix it. Why do we ever bother telling the user that an error has occurred and to try again with an error log?
  6. What are the advantages of logging all requests?
  7. Why do we sometimes have to use async move?