mirrors/system-design-primer
1
0
Fork 0
mirror of https://github.com/donnemartin/system-design-primer.git synced 2025-12-14 17:08:56 +03:00
Code Issues Projects Releases Wiki Activity

feat: add cache write-behind disadvantage

Browse Source
This commit is contained in:
eylon.basirtman
2024-01-06 10:31:59 +02:00
parent a07e261677
commit 52c460eaeb
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@@ -1268,8 +1268,9 @@ Write-through is a slow overall operation due to the write operation, but subseq
##### Disadvantage(s): write through
* When a new node is created due to failure or scaling, the new node will not cache entries until the entry is updated in the database. Cache-aside in conjunction with write through can mitigate this issue.
* When a new node is created due to failure or scaling, the new node will not cache entries until the entry is updated in the database. Cache-aside in conjunction with write through can mitigate this issue.
* Most data written might never be read, which can be minimized with a TTL.
* Failure in "Store in the DB" may lead to cache storing data that was never committed to the database. For a strong consistency, it's necessary to update the cache and the database in a distributed transaciton that will roll back the cache in case of database failure. This adds complexity to the system.
#### Write-behind (write-back)