What's the point of async/await in an ASP.NET Core application?

What’s the point of async/await in an ASP.NET Core application? There must be a good reason we “pollute” our code with async, await, tasks and so on, given the “old” way of writing C# code looked way cleaner.

When chatting to folks, it’s not often that someone can explain successfully why do we do this, so let’s see if this video is helpful in improving the understanding of the basics behind this subject.

🔔 Subscribe: https://youtube.com/CodingMilitia
✍️ Blog: https://blog.codingmilitia.com
🐦 Twitter: https://twitter.com/joaofbantunes
🤵 LinkedIn: https://linkedin.com/in/joaofbantunes
💁‍♂️ Support the channel: https://www.buymeacoffee.com/joaofbantunes

🔗 Video related links:
– “There Is No Thread” by Stephen Cleary: https://blog.stephencleary.com/2013/11/there-is-no-thread.html
– async guidance doc by David Fowler: https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md
– Dotnetos Async Expert course: https://asyncexpert.com/
– Async all the things: https://www.youtube.com/watch?v=CGi1bQgaqwg