zero-to-production VS tokio

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/

Being able to control nondeterminism is particularly useful for testing and debugging. This allows creating reproducible test environments, as well as discrete-event simulation for faster-than-real-time simulation of time delays. For example, Cardano uses a simulation environment for the IO monad that closely follows core Haskell packages; Sui has a simulator based on madsim that provides an API-compatible replacement for the Tokio runtime and intercepts various POSIX API calls in order to enforce determinism. Both allow running the same code in production as in the simulator for testing.

tokio / hyper / toml / serde / serde_json / json5 / console

tokio - An asynchronous runtime for Rust

3. Tokio

The AWS SDK makes use of the async capabilities in the Tokio library. So when you see async in front of a fn that function is capable of executing asynchronously.

Petar is also looking at implementing concurrency the way it is in Go to have a fully functional virtual machine as it is in the spec. This would likely attract more external contributors to developing the VM. One advantage of Rust is that, with the concurrency model, there is already an extensive library called Tokio which he can use. Petar stresses that this isn’t easy, but he believes it’s achievable, at least as a research topic around determinism and concurrency.

Another thing to point out is that async is a thing in Rust. I'm not going to begin to dive into this paradigm in this article, but know it's handled by the awesome Tokio framework.

So I started by using Tokio, a popular async runtime. The docs and samples helped me get a simple outbound TCP connection working. The Rust async book also had a lot of good explanations, both practical and digging into the details of what a runtime does.

Regarding the quote:

> The Original Sin of Rust async programming is making it multi-threaded by default. If premature optimization is the root of all evil, this is the mother of all premature optimizations, and it curses all your code with the unholy Send + 'static, or worse yet Send + Sync + 'static, which just kills all the joy of actually writing Rust.

Agree about the melodramatic tone. I also don't think removing the Send + Sync really makes that big a difference. It's the 'static that bothers me the most. I want scoped concurrency. Something like <https://github.com/tokio-rs/tokio/issues/2596>.

Another thing I really hate about Rust async right now is the poor instrumentation. I'm having a production problem at work right now in which some tasks just get stuck. I wish I could do the equivalent of `gdb; thread apply all bt`. Looking forward to <https://github.com/tokio-rs/tokio/issues/5638> landing at least. It exists right now but is experimental and in my experience sometimes panics. I'm actually writing a PR today to at least use the experimental version on SIGTERM to see what's going on, on the theory that if it crashes oh well, we're shutting down anyway.

Neither of these complaints would be addressed by taking away work stealing. In fact, I could keep doing down my list, and taking away work stealing wouldn't really help with much of anything.

The PHP <-> Rust bindings are provided by https://github.com/Nicelocal/ext-php-rs/ (our fork of https://github.com/davidcole1340/ext-php-rs with a bunch of UX improvements :).

php-tokio's integrates the https://revolt.run event loop with the https://tokio.rs event loop; async functionality is provided by the two event loops, in combination with PHP fibers through revolt's suspension API (I could've directly used the PHP Fiber API to provide coroutine suspension, but it was a tad easier with revolt's suspension API (https://revolt.run/fibers), since it also handles the base case of suspension in the main fiber).