Скачать с ютуб Read-Through vs. Write-Through Caching – Which Cache Strategy Fits Your Application? в хорошем качестве

Read-Through vs. Write-Through Caching – Which Cache Strategy Fits Your Application?

A Read-Through Cache sits between your application and your data store. Here’s how it works: 1. Application Request – When the app needs data, it checks the cache first. 2. Cache Hit – If the data is there, the cache returns it directly—quick and efficient. 3. Cache Miss – If the data isn’t there, the cache itself loads the data from the database, stores it in the cache, then returns it to the application. This approach is often called “lazy loading,” because the cache only gets populated on a miss—when the data is first needed. ----------------------------------------------------------------------------------------------- In a Write-Through Cache, every write is simultaneously applied to the cache and to the underlying data store: 1. Application Write – The app writes data into the cache first. 2. Sync to Database – The cache immediately writes the same data to the database. 3. Completion – The write operation is only considered done when both writes succeed. This ensures the cache and the database remain in lockstep, preventing staleness right after a write.