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

View More author details

Table of Contents (27) Chapters

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

Why subscribe?

26. Other Books You May Enjoy

Implementing statelessness

Statelessness is where the server does not store any information about the client session. The advantages here are straightforward. It enables our application to scale more easily as we free up resources on the server side by storing session information on the client’s side instead.

It also empowers us to be more flexible with our computing approach. For instance, let’s say that our application has exploded in popularity. As a result, we may want to spin our app up on two computing instances or servers and have a load balancer direct traffic to both instances in a balanced manner. If information is stored on the server, the user will have an inconsistent experience.

They may update the state of their session on one computing instance, but then, when they make another request, they may hit another computing instance that has outdated data. Considering this, statelessness cannot just be achieved by storing everything in the client. If our...