My motivation for this question is because I am creating a .net web API project that would be using an existing neo4j rest api client that has synchronous methods. I\'d lik
I'd like to take advantage of some of the performance gains by going to asynchronous methods, but I want to avoid going into the neo4j api library and refactoring the synchronous methods to return async methods.
Sorry, you lose all the benefits of async on the server side if you just wrap synchronous code in Task.Run.
async is good on servers because asynchronous operations scale better than threads. But if you're using Task.Run, then you're using a thread anyway.