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, join this session on async best practices for ASP.NET Core.
Kevin is a freelance solution architect, Pluralsight author & consultant, living in Antwerp (Belgium). These days he's mainly focused on architecture & security for web and mobile applications, using .NET.
He's a Microsoft MVP, and a keen proponent of open-source software.
Location: Ordina, Blarenberg 3b, 2800 Mechelen
18h CET: Food
19h CET: Start of the session
An error has occurred. This application may no longer respond until reloaded.