You're reading from Rust Web Programming A hands-on guide to developing, packaging, and deploying fully functional Rust web applications

Product type Paperback

Published in Jan 2023

Publisher Packt

ISBN-13 9781803234694

Length 666 pages

Edition 2nd Edition

Languages

Rust

Tools

Rocket

Concepts

Server Side Web Development

Author (1):

Maxwell Flitton

Preface

1. Part 1:Getting Started with Rust Web Development FREE CHAPTER

2. Chapter 1: A Quick Introduction to Rust

3. Chapter 2: Designing Your Web Application in Rust

4. Part 2:Processing Data and Managing Displays

5. Chapter 3: Handling HTTP Requests

6. Chapter 4: Processing HTTP Requests

7. Chapter 5: Displaying Content in the Browser

8. Part 3:Data Persistence

9. Chapter 6: Data Persistence with PostgreSQL

10. Chapter 7: Managing User Sessions

11. Chapter 8: Building RESTful Services

12. Part 4:Testing and Deployment

13. Chapter 9: Testing Our Application Endpoints and Components

14. Chapter 10: Deploying Our Application on AWS

15. Chapter 11: Configuring HTTPS with NGINX on AWS

16. Part 5:Making Our Projects Flexible

17. Chapter 12: Recreating Our Application in Rocket

18. Chapter 13: Best Practices for a Clean Web App Repository

19. Part 6:Exploring Protocol Programming and Async Concepts with Low-Level Network Applications

20. Chapter 14: Exploring the Tokio Framework

21. Chapter 15: Accepting TCP Traffic with Tokio

22. Chapter 16: Building Protocols on Top of TCP

23. Chapter 17: Implementing Actors and Async with the Hyper Framework

24. Chapter 18: Queuing Tasks with Redis

25. Index

26. Other Books You May Enjoy

Questions

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 must wrap them in an enum instead?
How do we add a new version of views but still support the old views in case our API is serving mobile apps and third parties that might not update instantly?
Why is the stateless constraint becoming more important in the era of elastic cloud computing?
How could we enable another service to be incorporated utilizing the properties of the JWT?
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?
What are the advantages of logging all requests?
Why do we sometimes have to use async move?