In a write-through cache, the data is written to the cache and to the disk before returning to the writing process to continue.
在write - through cache模式下，在返回到写入流程并继续之前，数据将写入到缓存然后再写到磁盘。
In a write-behind cache, data reads and updates are all serviced by the cache, but unlike a write-through cache, updates are not immediately propagated to the data store.
在write - behind缓存中，数据的读取和更新通过缓存进行，与write - through缓存不同，更新的数据并不会立即传到数据库。
8K stripe size RA-WT (write ahead/write-through) cache (C: for OS; D: for Utils; E: for Scanmail quarantine; F: for Domino files and data)
8Kstripesize RA-WT (writeahead/write-through)缓存（C：用于OS；D：用于实用程序；E：用于Scanmail 隔离；F：用于Domino文件和数据）
For example, read and write requests to the underlying device drivers migrate through the buffer cache.
例如，对底层设备驱动程序的读写请求会通过缓冲区缓存来传递。
Write-through caching pattern is used by the applications to write data to the cache which causes writes to an underlying resource (e.g. a database).
直写式缓存模式被用于将数据写入底层资源(如数据库)的缓存。
The second change was adding another write-through Row Cache containing database records: users and tweets.
第二个改动是加入另一个直写式行缓存，它包含了数据库记录：用户和tweets。
The first architectural change was to create a write-through Vector Cache containing an array of tweet IDs which are serialized 64 bit integers.
第一个架构改动是创建一个直写式向量缓存包含了一个tweetID的数组，tweet ID是序列化的64位整数。
This scenario also has faster response times than the write-through caching scenario where an update to the cache results in an immediate update to the database.
它比write - through缓存具有更快的响应时间，后者对缓存的更新会导致对数据库的及时更新。
It is expected that for a system using write behind that all changes are made through the cache and through no other path.
可以预见，采用write -behind的系统，作出变更的唯一路径就只能是缓存。
The distributed lock system is used to synchronize GOS steps when accessing data. The consistency of the distributed cache is guaranteed by updating strategies of write-through and write-invalidate.
分布式锁管理机制实现了GOS之间数据访问的同步协调，写通和写—无效的数据更新策略保证了GOS的缓存一致性。
The distributed lock system is used to synchronize GOS steps when accessing data. The consistency of the distributed cache is guaranteed by updating strategies of write-through and write-invalidate.
分布式锁管理机制实现了GOS之间数据访问的同步协调，写通和写—无效的数据更新策略保证了GOS的缓存一致性。
应用推荐