title: Understanding Redis, the concept of caching in general
body: <p>I'm working on a web app that gets data from an API provider. It's getting the data I need but I need a way to cache this data to keep from calling them again for the same data.</p>
  
  <p>Then I stumbled on Redis which seems to serve my purpose but I'm not 100% clear about the concept of caching using Redis. I've checked their documentation but I don't really follow what they have to say.</p>
  
  <p>Let's suppose I have just deployed my website to live and I have my first visitor called A. Since A is the first person that visits, my website will request a new set of data over API provider and after a couple seconds, the page will be loaded with the data that A wanted.</p>
  
  <p>My website caches this data to Redis to serve future visitors that will hit the same page. </p>
  
  <p>Now I have my second visitor B. </p>
  
  <p>B hits the same page url as A did and because my website has this data stored in the cache, B is served from the cache and will experience much faster loading time than what A has experienced.</p>
  
  <p>Is my understanding in line with with the concept of web caching?</p>
  
  <p>I always thought of caching as per user basis so my interaction on a website has no influence or whatsoever to other people but Redis seems to work per application basis.</p>