CODEWITHSUNDEEP
c#asp.net.netasp.net-mvcasp.net-web-api
user4715853
user4715853

Reputation:

Proper use of async/await in Web API

I have an existing Business Library, which I want to expose using Web API. My existing business classes looks like

public class Business
{
    public bool DoSomeBusiness()
    {
        //Performing long running  DB operations
        return true;
    }
    //Other methods
}

I am writing a Web API method like following code and using asyn/await for better scalability.

public class SampleController : ApiController
{
    Business _business;
    public ValuesController(Business business)
    {
       _business = business;
    }
    public async Task<HttpResponseMessage> Get()
    {
       var result= await Task.Run(() => _business.DoSomeBusiness());
       return Request.CreateResponse(HttpStatusCode.OK, result);
    }
}

Is this approach correct? Will I get the real benefit of the asynchronous behaviour? I don’t want to change my existing business layer implementation to make them task based.

Upvotes: 4

Views: 4709

Answers (1)

usr
usr

Reputation: 171178

This accomplishes nothing. If it did, ASP.NET could just run your action in a Task.Run call automatically and achieve better scalability.

You can't cheat this. You need to use async all the way down to the IOs you're making. This infects everything which is why this should be done when needed and not by default.

I'll link you two basic posts about making this choice because right now you do not understand the topic enough to make the choice:

https://stackoverflow.com/a/25087273/122718 Why does the EF 6 tutorial use asynchronous calls? https://stackoverflow.com/a/12796711/122718 Should we switch to using async I/O by default?

Upvotes: 9

Related Questions