2021-03-21 13:45:39 +03:00
|
|
|
+++
|
|
|
|
|
noatcards = True
|
|
|
|
|
isdraft = False
|
2021-03-27 13:16:09 +03:00
|
|
|
weight = 145
|
2021-03-21 13:45:39 +03:00
|
|
|
+++
|
|
|
|
|
|
|
|
|
|
# Write-behind (write-back)
|
|
|
|
|
|
|
|
|
|
## Introduction
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[Source: Scalability, availability, stability, patterns](http://www.slideshare.net/jboner/scalability-availability-stability-patterns/)
|
|
|
|
|
|
|
|
|
|
In write-behind, tha application does the following:
|
|
|
|
|
|
|
|
|
|
- Add/update entry in cache
|
|
|
|
|
- Asynchronously write entry to the data store, improving write performance
|
|
|
|
|
|
|
|
|
|
## Disadvantage(s) : write-behind
|
|
|
|
|
|
|
|
|
|
- There could be data loss if the cache goes down prior to its contents hitting the data store.
|
|
|
|
|
- It is more complex to implement write-behind than it is to implement cache-aside or write-through.
|
