Getting started with Tokio. The ultimate starter guide to writing async Rust.

Async Rust is one of the more exciting developments of the last few years, and Tokio is a powerful framework to enable asynchronous code, which can provide performant and scalable solutions.

It's also scary and daunting to tackle without any understanding. This video aims to be the ultimate starter guide for writing async code with Tokio, and how to achieve performant code that's both blocking and non-blocking

My socials:

#rustlang #tokio #async #coding #programming #developers #frameworks #framework #await #asynchronous #nonblockingio

00:00 Intro
00:12 Getting Started
01:46 Non Blocking IO
02:52 Futures
04:39 Tokio Features

[TheRealKitWalker]

Wow. Appreciate the hard work in compiling all this information in a precise way. Thanks. Very refreshing.

[r_rho]

Easily the best explanation ive seen on tokio. Thanks for this!

[BooTheDev]

Super cool video! I was confused about async in rust for a long time but could not find the great one like this. Thanks!

[skytech]

Awesome guide to async! Please make the follow-ups for other tokio async modules. Thanks 👍

[brivism]

Wtf man. This content is pure gold!
Love the quality 🔥🔥

[TechBuddy_]

This is by far the best explanation of tokio, this is just fantastic. I love you man 💓

[aaronraycove]

Your video didn't directly address the issue I was running across. But thanks for explaining this in more detail, because having that understanding helped me figure out the issue I was having. This is awesome Thanks so much.

[sparschaler]

Great video.
Thanks for not begging me to subscribe, which I had already done half way through.

[foxcirc]

I prefer smol/async-executor. It is much more lightweight and compiles like 10x faster. The only issue is that there are less libraries written for it then there are for Tokio, but this has not been that big of a deal for me.

[jeffreyefemena]

best explanation to tokio i've seen thank you

[nurmohammed]

Appreciate your hard work!

Reading from file in async context does not boost performance, because OS generally does not provide async API,
Tokio spawn a thread from thread pool to work with file.

[programmingfunda]

thanks, keep motivating us towards rust <3

[a]

Great content. Please do a video about structured concurrency in rust.

[sndb]

How did you made your terminal to this beautiful theme?

[MrKeebs]

Incredible intro and channel. Have a sub! Thank you! <3

[haliszekeriyaozkok]

Tokio is not a framework, it is a runtime. There is huge difference between each other. Axum, rocket etc is frameworks and they depending on tokio runtime.

[gosnooky]

Been starting at that code at 6:00, and I can't figure out how it sorts those strings.

[anonymmc]

Great content! I have one question regarding the futures though: If the future is only executed once await is called (generally speaking) that implies we would lose some performance here, would it not? Let's say we have an async database call. If we were to execute the call right away it might have completed already once we await it. But since execution is lazy it's only executed once we await it. This might not be a huge problem since we can use our resources for something else while awaiting the database's response (due to the use of a thread pool) but it would still add to our overall latency, would it not? Or do I have a fundamental misunderstanding of lazy execution in this context?

[motbus]

2:20 if you build release mode, it seems it resolves it automatically

[justafreakable]

Question: why rust doesn't have a std lib async runtime? Or is tokio better ?