Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Rust Web Programming
  • Table Of Contents Toc
  • Feedback & Rating feedback
Rust Web Programming

Rust Web Programming

By : Maxwell Flitton
3.5 (6)
close
close
Rust Web Programming

Rust Web Programming

3.5 (6)
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)
close
close
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. What are the advantages of defining unique constraints in the SQL as opposed to the server-side code?
  2. What is the main advantage of the user having a JWT over storing a password?
  3. How does a user store a JWT on the frontend?
  4. How could the JWT be useful in the view once we have verified that the JWT is passable?
  5. What is the minimal approach to altering data in the frontend and redirecting it to another view when the user hits an endpoint?
  6. Why is it useful to have a range of different response codes when logging in a user, as opposed to just denoting that it is successful or not successful?

Limited Time Offer

$10p/m for 3 months

Get online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech and supported with AI assistants
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon

Create a Note

Modal Close icon
You need to login to use this feature.

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note