why are all database access methods within the asp.net Identity api marked async
asp.net, asp.net-identity, async-await
Solution
This is more general question about `async-await`. Methods executed this way are not blocking the executing thread and application is available to do other work, while DB is returning with the result. This means that your application can serve other request (from other user perhaps) while waiting for DB to return the result.
There are a lot have been written about `async-await`. You can start from here: http://blogs.msdn.com/b/cdndevs/archive/2013/12/18/c-async-and-await-why-do-we-need-them-part-1.aspx
And, FYI, Identity library have non-async methods provided as extension methods. So if your application is non-async, you don'have to use `async` keywords all the way through your app.
Problem
Consider this simple pseudo code ``` User logs in Application access database to try retrieve the login using provided password and username if record is found then show requested page otherwise display login with error message ``` How does this benefit from being async? Surely the application can't continue until the database has searched for the record.