Re:SQLite briefing for Linux kernel hackers (2019)
by twhitmore on Saturday November 21, 2020 @06:31PM
(#25173536)
Files are a good abstraction to start from.
But to be honest, persistence & durability of data are the goal of Storage and thus what the filesystem API needs to be designed for.
The API needs to clearly be designed for atomicity, durability & to allow coordination across multi-file structures.
This can be achieved by either 1) indicating all required synchronizations to callers in metadata, or 2) fully encapsulating durability by making the API atomically commit every operation.
I don't agree these factors should be hidden, since a losing/ corrupting data are fundamentally at odds with the goals of a Storage API.
It's not just SQLite, any application needing to maintain a datastore needs reliable storage.
But to be honest, persistence & durability of data are the goal of Storage and thus what the filesystem API needs to be designed for.
The API needs to clearly be designed for atomicity, durability & to allow coordination across multi-file structures.
This can be achieved by either 1) indicating all required synchronizations to callers in metadata, or 2) fully encapsulating durability by making the API atomically commit every operation.
I don't agree these factors should be hidden, since a losing/ corrupting data are fundamentally at odds with the goals of a Storage API.
It's not just SQLite, any application needing to maintain a datastore needs reliable storage.