title: Best way to implement request throttling in ASP.NET MVC?
body: <p>We're experimenting with various ways to throttle user actions in a <strong>given time period</strong>:</p>
  
  <ul>
  <li>Limit question/answer posts</li>
  <li>Limit edits</li>
  <li>Limit feed retrievals</li>
  </ul>
  
  <p>For the time being, we're using the Cache to simply insert a record of user activity - if that record exists if/when the user does the same activity, we throttle.</p>
  
  <p>Using the Cache automatically gives us stale data cleaning and sliding activity windows of users, but how it will scale could be a problem.</p>
  
  <p>What are some other ways of ensuring that requests/user actions can be effectively throttled (emphasis on stability)?</p>