Best Practices for Building Async APIs with ASP.NET Core

Did you know the main driver for async isn't performance but scalability? Ever wondered why it makes sense to async I/O-bound tasks, but why doing the same with a long-running algorithm can actually hurt scalability? Or why using .Result on a Task in ASP.NET can result in a deadlock but perfectly works in ASP.NET Core - yet you still shouldn't use it? For answers to all of that and more, watch this recorded webinar session on async best practices for ASP.NET Core.

0:06 Intro
2:36 Why write asynchronous code?
15:12 The async/await keywords
20:20 Async return types
26:00 Demo time
42:30 I/O bound vs. computational bound work
57:40 What about legacy code?
1:01:16 What about the synchronization context?
1:22:20 Wrap up and Q&A

About the Presenter:
Kevin Dockx is a freelance solution architect, Pluralsight author & consultant, living in Antwerp (Belgium). These days he's mainly focused on RESTful architectures & security for web applications and mobile applications. He's a Microsoft MVP, and a keen proponent of open-source software.

Тэги:

#JetBrains #software_development #developer_tools #programming #developer #Rider #ReSharper #.NET #ASP.NET #API #Async #Kevin_Dockx #webinar

Скачать видео