From 3c817b672b716917f2e7cbad1f6eb6495367ebee Mon Sep 17 00:00:00 2001 From: Ido Ophir Date: Mon, 7 Apr 2025 12:07:44 +0300 Subject: [PATCH] Update README.md Copilot fix Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index b58c11aa..ce7f51dc 100644 --- a/README.md +++ b/README.md @@ -1310,8 +1310,7 @@ Write-through is a slow overall operation due to the write operation, but subseq * 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. - +* 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 transaction that will roll back the cache in case of database failure. This adds complexity to the system. #### Write-behind (write-back)