<ul>
<li>Read through
<ul>
<li>When you read something, it checks the cache to see if it is there
</li>
<li>If it's not in the cache, it will put it in the cache
</li>
<li>This means data will always exist in the cache, unless the data doesn't exist
</li>
</ul>
</li>
<li>Write through
<ul>
<li>When you write to the database, it will also write it to the cache
</li>
<li>Also known as write aside caching
</li>
</ul>
</li>
<li>Write behind
<ul>
<li>When you write to the cache, the cache knows how to persist the data to the database</li>
</ul>
</li>
</ul>
Azure only supports write through caching

* **Read through**
    
    * When you read something, it checks the cache to see if it is there
        
    * If it's not in the cache, it will put it in the cache
        
    * This means data will always exist in the cache, unless the data doesn't exist
        
* **Write through**
    
    * When you write to the database, it will also write it to the cache
        
    * Also known as write aside caching
        
* **Write behind**
    
    * When you write to the cache, the cache knows how to persist the data to the database
        

Azure only supports write through caching

Different types of caching

I'm an iOS developer, helping millennials with their finances through US neo-bank, Empower.
Before making the switch to development, I was a strategist and GM in the tech space.
