Daniel Marbach shows how to avoid common pitfalls in asynchronous code bases. Learn how to: * Differentiate between IO-bound vs CPU-bound work and how this relates to Threads and Tasks * Avoid serious production bugs as a result of asynchronous methods returning void * Opt-out from context capturing when necessary * Deal with synchronous code in the context of asynchronous code

1. Async best-practices
Welcome
webinar

2. Solution Architect
Enthusiastic Software Engineer
Microsoft MVP for systems integration
@danielmarbach
particular.net/blog
planetgeek.ch

3. Goals
CPU-bound vs IO-bound
Threads and Tasks
Async best-practices
target

4. Terminology Code WrapUp

6. Terminology Code WrapUp

7. event-driven
async

8. Task
uniform

9. Task
IO-bound

10. Task
CPU-bound

11. concurrent
interleaved

12. parallel
simultaneous

13. Continuation
function

14. Terminology Code WrapUp

15. async/await
simplicity
function1(function(err,res) {
function2(function(err,res) {
function3(function(err,res) {
function4(function(err,res) {
function5(function(err,res) {
// do something useful
})
})
})
})
})

16. cleanLaundry.ContinueWith(t => {
dryLaundry;
})

17. await cleanLaundry;
dryLaundry;

18. Demoawait

19. Terminology Code WrapUp

20. Forget thread!
think

21. NSB v6
Will be Async all the way
Applies the shown best-practies like
ConfigureAwait(false)consequently,
checked with Roslyn analyzer
particular.net/blog/async-await-its-time

22. Recap
Use Task.Run, Factory.StartNew for
CPU-bound work
Use Task directly for IO-bound work
Use async Task insteadof async void
reminder

23. Recap
Librariesand frameworks should use
ConfigureAwait(false)
Async all the way, don’t mix blocking
and asynchronous code
reminder

24. Next
particular.net/async-await-webinar-series

25. github.com/danielmarbach/02-25-2016-AsyncWebinar
Slides, Links…

26. Q & Aawait

27. Thanks