You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FKVS currently stores data in memory. Snapshot persistence is needed if FKVS is expected to recover state after restart or crash. This issue tracks RDB-style point-in-time persistence.
Related PR: #69 proposes an implementation and should be reviewed against the acceptance criteria below.
Scope
Serialize the key/value store and TTL metadata to disk.
Load snapshots on startup before accepting client traffic.
Discard expired keys during load.
Write snapshots atomically using temp file + fsync + rename.
Include format versioning and corruption detection.
Add configuration for snapshot path and save interval/threshold.
Define behavior for disabled persistence.
Acceptance criteria
Restarting the server restores non-expired keys from a snapshot.
Corrupt or partial snapshot files are detected and handled safely.
Snapshot writes cannot leave the configured snapshot path with a torn file.
Snapshotting has tests for strings, integer encoding, TTLs, expired keys, empty DB, missing files, and corrupt files.
README/server config docs explain the durability guarantees and limitations.
Activity
feat: implement snapshot-based persistence (closes AlexJuca#39)