I was looking at Maple's local mode and noticed that it already treats embedded chDB as a real local store, not just a temporary cache. The unclean-shutdown handling and local-store migration flow also suggest that recovery semantics matter a lot for this mode.
That made me wonder whether chdb-durable could be a useful fit here.
chdb-durable is a durable mode for embedded chDB: it keeps authoritative state in object storage or a local durable namespace, restores from checkpoints plus WAL replay, and uses a single-writer lease.
Potential value for Maple:
- Recover local telemetry after process crash or machine restart.
- Avoid wiping/rebuilding the local chDB store after dirty shutdowns.
- Store local-mode state in S3/R2/GCS/Azure/local durable storage.
- Checkpoint after successful local-store migrations.
Today chdb-durable is mainly exposed from Python. If this direction sounds useful, the chDB side can help contribute a JS/TypeScript, Bun, or sidecar durable integration and discuss the Maple-side changes together.
I was looking at Maple's local mode and noticed that it already treats embedded chDB as a real local store, not just a temporary cache. The unclean-shutdown handling and local-store migration flow also suggest that recovery semantics matter a lot for this mode.
That made me wonder whether chdb-durable could be a useful fit here.
chdb-durable is a durable mode for embedded chDB: it keeps authoritative state in object storage or a local durable namespace, restores from checkpoints plus WAL replay, and uses a single-writer lease.
Potential value for Maple:
Today chdb-durable is mainly exposed from Python. If this direction sounds useful, the chDB side can help contribute a JS/TypeScript, Bun, or sidecar durable integration and discuss the Maple-side changes together.