---
title: "Comment by Gilbert Jimmie on \"Bitcask - a log-structured fast KV store\" | Hashnode"
description: "Since append-only writes are strictly sequential and do not necessitate seeking, they can be performed at any time without interruption. All writes are read-thr"
url: "https://hashnode.com/posts/bitcask-a-log-structured-fast-kv-store/5f145b90d27eb64b689dda87/comment/6364906a6966069239a87e16"
---

[Discussion](https://hashnode.com/posts/bitcask-a-log-structured-fast-kv-store/5f145b90d27eb64b689dda87)

Comment [Bitcask - a log-structured fast KV store](https://hashnode.com/posts/bitcask-a-log-structured-fast-kv-store/5f145b90d27eb64b689dda87)

[Gilbert Jimmie](https://hashnode.com/@SaraPaul)

[Nov 4, 2022](https://hashnode.com/posts/bitcask-a-log-structured-fast-kv-store/5f145b90d27eb64b689dda87/comment/6364906a6966069239a87e16)

Since append-only writes are strictly sequential and do not necessitate seeking, they can be performed at any time without interruption. All writes are read-throughs [spin the wheel](https://spin-thewheel.com/) . The disk-based data file is appended whenever a value is modified, and the in-memory key index is subsequently updated to reflect the new location of the file.
