Oct 29, 2024

Some of the other areas of importance not discussed are, mmap: store must be fully write/write, read/write, and read/read concurrent and lock-free. mmaps grow and must be independently (by file) remapped, but that invalidates every outstanding pointer into the map. heavily concurrent reading and writing can cause mmaps to thrash. process termination with a mmap unflushed corrupts the file data. snapshotting (or pausing to snapshot) a live mmap implies transactional commit. automatic snapshotting, fault detection, and recover, as well as hot backup are crazy features to be able to provide given above, not to mention that it takes about a minute to snapshot the store while running.