Crates.io | walr |
lib.rs | walr |
version | 0.1.6 |
source | src |
created_at | 2024-10-12 23:26:27.990928 |
updated_at | 2024-10-29 21:41:43.784236 |
description | Write Ahead Log(WAL) implementation using tokio |
homepage | |
repository | https://gitlab.com/robertlopezdev/walr |
max_upload_size | |
id | 1406948 |
size | 38,374 |
Ergonomic Write Ahead Log(WAL) using tokio
cargo add walr
A WAL has two generics:
Log
: The type of the Log to write to disk
State
: The state wanting to be persisted
Generally, you construct a WAL, call WAL::replay
to replay the State
from disk,
start applying logs via WAL::log
and WAL::log_many
; then when WAL::should_checkpoint
is true
, you checkpoint the in-memory State via WAL::checkpoint
. If your mutable action
on State
in not infallible, WAL::undo
will undo the last log or log many operation.
Example (Persisting a basic Cache)
Log
= CacheLog
State
= Cache
type Cache = HashMap<String, String>;
#[derive(Serialize, Deserialize)]
enum CacheLog {
Remove(String),
Insert { key: String, value: String },
}
Where the Log
type captures all enumerates of mutable actions on State
. Then, using these logs through replay
with a replay handler, you can replay the State
.
fn replay_handler(
logs: Vec<CacheLog>,
checkpoint: Arc<Mutex<Cache>>,
) -> ReplayHandlerResult {
Box::pin(async move {
let mut checkpoint = checkpoint.lock().await;
for log in logs {
match log {
CacheLog::Insert { key, value } => checkpoint.insert(key, value),
CacheLog::Remove(key) => checkpoint.remove(&key),
};
}
Ok(())
})
}
See exmaple.rs
for the full example.
See Full crate documentation here at docs.rs for all available functionality.
Open to contributions, please just create a PR/issue or reach out to me to discuss what you would like to add/change.
MIT License
Copyright (c) 2024 Robert Lopez
See LICENSE.md