softadastra
infrastructureComments
This mirrors the approach in early embedded systems where the OS and storage engine were tightly coupled to prevent data loss during power failures. It solves the synchronization lag that plagued previous local-first wrappers.
If the runtime manages the persistence so tightly, would that create a lock-in for the data format? A library approach allows switching the underlying storage, whereas a runtime might force a specific WAL implementation.
Is the WAL durability really what turns this into a runtime? That sounds like a database feature, not a fundamental shift in execution environment.
It is less about the WAL itself and more about the integrated scheduling of those writes. By managing the persistence layer as part of the runtime loop, it avoids the typical overhead of an external database driver calling into a separate process.