Is there a difference in Async execution vs non-async execution in WebAPI ASP.NET Core controllers?

Question

Is there a difference between calling a method of service with async/await:

    [HttpPost]
    public async Task<SmthResponce> AddSmth([FromBody] SmthRequest smthRequest)
    {
        return await smthsService.AddSmthAsync(smthRequest);
    }

and without:

    [HttpPost]
    public Task<SmthResponce> AddSmth([FromBody] SmthRequest smthRequest)
    {
        return smthsService.AddSmthAsync(smthRequest);
    }

Ask yourself this question: How will I get the values from your two examples? Hint: var x = AddSmth("test"); y = x; — Big Daddy
– Big Daddy, Commented Apr 4, 2018 at 17:24
There are some subtle differences between the two: blog.stephencleary.com/2016/12/eliding-async-await.html. How much these will affect you depends on the implementation of AddSmthAsync. However, I assume they typically shouldn't have any effect for Web API. — Douglas
– Douglas, Commented Apr 4, 2018 at 17:29

glenebob · Accepted Answer · 2018-04-04 15:56:32Z

3

From the callers perspective, there is no difference; however...

The first method (await) involves the creation of an additional Task, which will be completed when the inner Task completes.

The second method (returning the Task directly, when possible) is preferred.

answered Apr 4, 2018 at 15:56

glenebob

1,99311 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Is there a difference in Async execution vs non-async execution in WebAPI ASP.NET Core controllers?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related