one simple question. I found some methods with this "logic" and "architecture".
public async Task<T> FindAsync(params object[] keys)
{
return await this.context.FindAsync(keys);
}
One single instruction with its await. Since the method is async you have to do this (otherwise compiler errors occur). IMHO i can't find why you should use this pattern because if the method is async you probably want to perform different tasks in parallel. If you sync the execution with the await keyword you make the method close to sync and you loose all the performance gain of the managed thread pool mechanism of .net. What is your opinion? I'm in wrong?
awaitdoesn't make code synchronous.async/awaitdon't have anything to do with the thread pool. You may find myasyncintro helpful.