title: In an asynchronous ASP.NET Web API with a lot of traffic, what is the impact of setting ConfigureAwait false?
body: <p>I'm working on a new <code>API</code> that will eventually receive a very large amount of traffic. I was initially under the impression that I'd want to set <code>ConfigureAwait(false)</code> through my full <code>async</code>/<code>await</code> stack, but after attempting to debug some <code>application insights</code> <code>tracing</code> I found out that certain values in the <code>HttpContext</code> are lost if I use <code>ConfigureAwait(false)</code>.</p>
  
  <p>Can anybody with some high traffic <code>API</code> experience tell me anything else I might be missing that could be impacted by having <code>ConfigureAwait(false)</code> like is it possible for a user to receive the output from a different user's request?</p>
  
  <p>What would be the impact of removing all <code>ConfigureAwait(false)</code> statements in my <code>API</code>?</p>