Back to Basics: Efficient Async and Await - Filip Ekberg - NDC Oslo 2023
32,288
Published 2023-06-23
That's right, no one likes applications crashing or giving users an unexpected behavior.
Introducing asynchronous patterns is so much more than just applying async and await to your methods; you really, I mean really, need to understand what's going on.
In this session, we'll make sure you know how to avoid crashing your applications, and how to adhere to best practices when applying asynchronous patterns in our .NET applications.
Check out our new channel:
NDC Clips:
@ndcclips
Check out more of our featured speakers and talks at
ndcconferences.com/
ndcoslo.com/
All Comments (19)
-
I really like the approach of explaining the role of the Task class before explaining Async and Aeait
-
The joke at the beginning was great! 🤣
-
Really useful. Clears a lot of my concerns on using these asynchronous keywords and concept. Great talk, Filip. Cheers!
-
Thank you for share your knowledge.
-
It's was good material, thanks for sharing!
-
Great talk!
-
Awesome
-
I almost clicked away.
-
Regarding the statements on ConfigureAwait, does this mean we no longer need to add .ConfigureAwait(false) on "library code"?
-
50:47 Streams
-
Did you just rick-roll the whole audience?
-
13:50 don't be fooled, while this may be funny now, reading code with bad naming conventions several days later will have you pulling your hairs out.
-
58:30 This makes no sense. In a .Net Core WPF, you still need to do things on the UI thread. Or are you expected to use the Dispatcher for all the UI code in an async method?
-
I wish he'd explained the generated code better.
-
Nice, but like other presentations, avoids practical stuff, like call async from constructor.
-
Sad to see that in 2023 the author was not able to pick a better topic for his talk than the one that has already been covered dozens of times in books, articles, video courses etc. Disappointed 😿
-
4:30 "you don't want to block that operation". Yes, I do. I very much want to block these operations. This is because most of the time the rest of the program relies on successful storage or retrieval of this data. I've worked on numerous web applications, some of which are public facing, serving thousands of users at the same time. And never did I experience thread starvation or extreme lagginess because of those waits. Async await is nice for apps (actually was invented because MS wanted to create Windows Phone). But not needed for web applications. Complete overkill. Web applications are already asynchronous by nature.
-
Anyone who has to watch it inevitably falls asleep. Who thinks it's great? Only the makers themselves. Groan-
