Action in Controller is already in a different thread, why do we still need to use async/await? I was looking at: https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?view=aspnetcore-3.1&tabs=visual-studio#examine-the-posttodoitem-create-method I see it has a action in this controller: [HttpPost] public async Task> PostTodoItem(TodoItem todoItem)
So, I did a few test in my own controller, I see when I send a request from my browser, the server side always create a new worker thread to handle the request, so that's why I had the doubt: if the controller is already handling request in different thread, why should I still use async/await? Since the request being handled in a new thread, I don't think it will block any other request.