Abort Controller and Cancellation Tokens | Cancel Your Work All the Way | ASP NET

Imagine this..

A user starts a resource-heavy task from your app's UI, such as processing extensive data or running a complex report.

Halfway through, they realize something's wrong and hit the cancel button. The UI responds
immediately, showing the task as canceled.

Problem solved, right?

Wrong!!

Canceling a long-running process from a UI form doesn't mean the server has stopped processing the work. Your server could still be chugging along, consuming precious resources for something no one wants anymore.

Depending on the kind of work, this could be more than inefficient—it could also be dangerous and lead to inconsistent states and misleading results.

So, how do you let the user cancel this work and ensure it gets canceled on the server?

That's where AbortControllers and Cancellation tokens come in, and that's exactly what we'll learn in this video.

Thanks to AWS for sponsoring this video.

00:00 Intro
2:02: Problem without Cancelling Work
6:20 Abort Controller

Additional Watching
📹Cancellation Token -    • Cancellation Token in .NET | Explorin...  
📹Cancellation Token Practices -    • Are You Using Cancellation Token The ...  
📹C# Series - https://bit.ly/mycsharp
📹 ASP Series - https://bit.ly/asp-net-core-series
📹Azure Series - https://bit.ly/azure-series
📹AWS Series - https://bit.ly/aws-net-series
📹RabbitMQ Series - https://bit.ly/rabbitmq-net-series

Come say hi! ✋
🎙️Uses - https://www.rahulpnath.com/uses
🌍Blog - https://www.rahulpnath.com/
✉ Subscribe to my Newsletter - https://www.rahulpnath.com/subscribe
🐦Twitter -   / rahulpnath  
📸Instagram -   / rahulpnath  

#dotnet #csharp #aspnetcore #aws