zero-to-production VS nomicon

Zero to Production in Rust - Book by Luca Palmieri: An in-depth book that guides readers through building a fully functional backend application in Rust, from zero to production.

And the book "Zero To Production In Rust - An introduction to backend development", I didn’t read it yet but seems pretty good

It’s a lot simpler if you add serde to the mix (derive Deserialize for your settings types). Have a look at the example from the Zero to Production book: https://github.com/LukeMathWalker/zero-to-production/blob/main/src/configuration.rs

You probably want to check out the Zero to Production book which is about using Rust for back-end development.

https://www.zero2prod.com/

If your'e more into a tutorial with a book https://www.zero2prod.com/ is really good. You gonna build a newsletter service. With all the good stuff in backend development.

If you want to build a backend in Rust, Axum (which uses hyper underneath) is pretty recommended these days, as it's all in the tokio ecosystem. Actix Web is good too, but it has its own ecosystem of libraries. I read the book Zero To Production in Rust [0] which was a great overview on not just Rust but scalable backend architectures as a whole.

Interestingly, Cloudflare wanted to use hyper but found that it was too correct, so they had to build their own [1].

[0] https://www.zero2prod.com

[1] https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...

In addition to the book, which has already been recommended. If you’re specifically into backend you should try Zero to Production. Luca really knows what he’s talking about, and it’s an excellent overview of backend rust and the development process in general.

I highly recommend the book Zero to Production in Rust which also has an associated GitHub. I like the style of the writing and the explanations used within the book. Even though it uses Rust, the concepts seem to work in any language - I have applied the concepts to both Go and Python in the past.

I would recommend you a book - "Zero to Production in Rust" https://www.zero2prod.com/

if you want to learn more about web backend development there is nothing better then https://www.zero2prod.com/

it’s even written by the same person that wrote the Nomicon (the guide to the dark arts of unsafe)

If you want to dive deeper you can always have other options but now there are concrete cases, if you want to do low level thing https://doc.rust-lang.org/nomicon/ while if you want multi thread/concurrency stuff https://marabos.nl/atomics/ . There are many many books so you will have to point yourself to what you want

Nonononono. SeqCst is the most error prone memory order: https://github.com/rust-lang/nomicon/issues/166

Hope this helps. For more details, see the Rustonomicon. I referenced the subtyping chapter here extensively.

Nice video! Glad I could help out. This stuff is hard, and I'm still learning a lot about it myself even years later. The Rustonomicon is a great read if you haven't already.

Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.

That is not what UB means. Undefined Behaviour is behaviour that the compiler is allowed to assume will never happen, and which can consequently cause miscompilations due to optimisation passes gone wrong if it does in fact occur in the source code.

It's true that Rust does not have a written specification that clearly delineates what is and isn't UB in a single place. But:

1. UB is impossible in safe code (modulo bugs in unsafe code)

2. There are resources such as the Rustinomicon (https://doc.rust-lang.org/nomicon/) that provide a detailed guide on what is and isn't allowed in unsafe code.

In practice, it's much easier to avoid UB in Rust than it is in C++.

However, this is a wide topic out of scope for a Reddit comment, so maybe just read the Rustonomicon. It explains everything about data handling in Rust.

The ownership model & borrow checker makes rust a bit of an awkward language in which to write complex data structures like trees and graphs. It can be done - since you can always use raw pointers & unsafe code when you absolutely need to to treat rust like C. But the language fights you, and the community can get a bit moralistic about this sort of thing. The rust nomicon is a fantastic resource for learning the limits of the borrow checker, and where and how to use unsafe code correctly. You will need unsafe less than you think you will, but sometimes you will have no choice.