Nov 21, 2019 08:51 PM|mgebhard|LINK
what is the difference or advantage to use a background worker like that instead of Task.Run? As far as i know they both use a thread from thread pool so in an MVC scenario i m still blocking an useful thread. Am i wrong?
The Task.Run() is called many times and create many threads. A queue process uses one thread. Queue the HTTP response. A background process dequeues items and processes them.
If Task.Run() is best for your application then use Task.Run(). It's just a matter of comparing pros and cons.