Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Rust Web Programming

You're reading from   Rust Web Programming A hands-on guide to Rust for modern web development, with microservices and nanoservices

Arrow left icon
Product type Paperback
Published in Nov 2025
Last Updated in Sep 2025
Publisher Packt
ISBN-13 9781835887769
Length 733 pages
Edition 3rd Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Maxwell Flitton Maxwell Flitton
Author Profile Icon Maxwell Flitton
Maxwell Flitton
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Rust Web Programming, Third Edition: A hands-on guide to Rust for modern web development, with microservices and nanoservices FREE CHAPTER
1 A Quick Introduction to Rust 2 Useful Rust Patterns for Web Programming 3 Designing Your Web Application in Rust 4 Async Rust 5 Handling HTTP Requests 6 Processing HTTP Requests 7 Displaying Content in the Browser 8 Injecting Rust in the Frontend with WASM 9 Data Persistence with PostgreSQL 10 Managing user sessions 11 Communicating Between Servers 12 Caching auth sessions 13 Observability through logging

Checking Struct State with the Compiler

There are times when a state of a struct and certain processes are just not appropriate anymore. A nice clear example would be a database transaction. While a database transaction is in progress, certain processes are appropriate such as adding another operation into the transaction. You may also want to commit your transaction or roll it back. However, once we have committed our transaction, we cannot roll it back or add another operation to the transaction, we need another transaction for this. Considering this, I would want my compiler to check and ensure that I am not passing in a transaction into certain functions once the transaction is no longer in progress. The compiler will not only give me instant feedback, it will also be safer, as it could be that only certain edge cases could cause a bug, increasing the chance of the bug slipping through tests.

To get this compiler checking, I need a state in my struct. I then need that state to change...

lock icon The rest of the chapter is locked
Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Rust Web Programming
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Modal Close icon
Modal Close icon