# Overview In a write-around cache... #flashcard The application writes data directly to the database. Data is read from the cache. If it is not present on the cache, the application reads the data from the database. Then, the application adds the data to the cache. <!--ID: 1751507776581--> ## Diagram ![[Write-around Cache 2024-12-19 09.40.14.excalidraw.svg]] %%[[Write-around Cache 2024-12-19 09.40.14.excalidraw|🖋 Edit in Excalidraw]]%% # Key Considerations # Pros The pros of write-around cache are: #flashcard - Reduces flooding the cache with data that may not be read <!--ID: 1751507776583--> # Cons The cons of write-around cache are: #flashcard - Recently written data will always result in a cache miss, causing an extended time for the read and subsequent write to the cache - Requires an emphasis on cache invalidation. If there is a hit on old data in the cache, the application won't know there is newer data in the database <!--ID: 1751507776586--> # Use Cases The use cases of write-around cache are: #flashcard - Write once, read-less-frequently scenarios <!--ID: 1751507776588--> # Related Topics