> Async doesn't do anything fundamentally new. This is correct, but not in the way you're describing. The API calls that it ultimately makes have been in plac

> Async doesn't do anything fundamentally new. This is correct, but not in the way you're describing. The API calls that it ultimately makes have been in place before C# 5. C# 5 just made writing that kind of code significantly simpler than it was before. > If you already implemented multithreading in your application that you're happy with, there's no compelling reason to switch to doing it the async way. This isn't necessarily true. From the perspective of a client application, it's less resource-intensive to use async code than to spin up another thread. On mobile devices that's less battery life used, which is always a good thing. From the perspective of a server, multithreading only gets you so far, plus they can eat up tons of memory in the process. Async code does not spin up new threads and allows for spikes in traffic to be handled gracefully rather than (a) using tons of threads, or (b) being unable to handle the load at all.