tracing VS zero-to-production

The video description is as follows:

In this stream, we peel back the crust on the tracing crate — https://github.com/tokio-rs/tracing/ — and explore its interface, structure, and mechanisms. We talk about spans, events, their attributes and fields, and how to think about them in async code. We also dig into what subscribers are, how they pick up events, and how you can construct your own subscribers through the layer abstraction. For more details about tracing, see https://docs.rs/tracing/latest/tracing/.

> What's been your biggest issues around ergonomics/amenities for OpenTelemetry?

I can't speak generally, but in the Rust ecosystem the various crates don't play well together. Here's one example: <https://github.com/tokio-rs/tracing/issues/2648> There are four crates involved (tracing-attributes, tracing-opentelemetry, opentelemetry, and opentelemetry-datadog) and none of them fit properly into any of the others.

The tracing (logging) mechanism in an asynchronous codebase (tracing).

Tracing is Tokio's alternative for async code.

At a technical level, in Rust, both [tracing]https://crates.io/crates/tracing) and log are entire ecosystems (though for the latter at least there's also third party logging frameworks), and there's at least a bridge from log to tracing.

I am using https://github.com/tokio-rs/tracing for logging purposes in my application. I would like to develop a feature wherein logs should be saved to a database table (via sea-orm). Something similar is this, but it does not solve my needs fully.

I've used the tracing infrastructure with tracing_flame to profile some hot paths in async code: https://github.com/tokio-rs/tracing/tree/master/tracing-flame

Oh nice! IIRC when I checked, it was the Unicode tables that smashed the code size. I recently hit the same issue with the tracing crate, where a crate feature (for env var filtering) pulled in regex and my binary was suddenly 1MB bigger.

I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.

tracing by itself only outputs log data, you need to consume them in a subscriber, the tracing-subscriber crate exists for this. (example)

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/