I noticed that HyperbyteDB already has serious recovery-related design: WAL, metadata, clustering, and derived chDB state. That makes this especially interesting, because chdb-durable may be able to complement the current architecture.
chdb-durable is a durable mode for embedded chDB: it stores chDB state in object storage or a local durable namespace, restores from checkpoints plus WAL replay, and uses a single-writer lease.
Potential value for HyperbyteDB:
- Restore chDB-derived state faster during cold recovery.
- Reduce the amount of existing WAL that needs to be replayed into chDB.
- Help new nodes bootstrap from durable chDB checkpoints.
- Complement existing archival/replication design without replacing it.
Today chdb-durable is mainly exposed from Python. If this direction sounds useful, the chDB side can help contribute a Rust durable API or sidecar and discuss the correct boundary with HyperbyteDB's WAL, schema/Raft, manifest, and recovery flow.
I noticed that HyperbyteDB already has serious recovery-related design: WAL, metadata, clustering, and derived chDB state. That makes this especially interesting, because chdb-durable may be able to complement the current architecture.
chdb-durable is a durable mode for embedded chDB: it stores chDB state in object storage or a local durable namespace, restores from checkpoints plus WAL replay, and uses a single-writer lease.
Potential value for HyperbyteDB:
Today chdb-durable is mainly exposed from Python. If this direction sounds useful, the chDB side can help contribute a Rust durable API or sidecar and discuss the correct boundary with HyperbyteDB's WAL, schema/Raft, manifest, and recovery flow.