title: WebApi - Redis cache vs Output cache
body: <p>I have been studying about Redis (no experience at all - just studied theory), and after doing some research, found out that its also being used as cache. e.g. StackOverfolow it self.</p>
  
  <p>My question is, if I have an asp.net WebApi service, and I use output caching at the WebApi level to cache responses, I am basically storing kind of key/value (request/response) in server's memory to deliver cached responses.</p>
  
  <p>Now as redis is an in memory database, how will it help me to substitute WebApi's output caching with redis cache?</p>
  
  <p>Is there any advantage?</p>
  
  <p>I tried to go through this answer <a href="https://stackoverflow.com/questions/19477821/redis-cache-vs-using-memory-directyly">redis-cache-vs-using-memory-directyly</a>, but I guess I didn't got the key line in the answer:</p>
  
  <p>"Basically, <strong>if you need your application to scale on several nodes sharing the same data</strong>, then something like Redis (or any other remote key/value store) will be required."</p>