3 ms·
Sure, querying that data is also important. Which means the question of “do you optimise for in-memory queries, or on disk queries” is important. Simply saying
by avianlyric 3y ago
Sure, querying that data is also important. Which means the question of “do you optimise for in-memory queries, or on disk queries” is important.
Simply saying you want the data to be durable isn’t that interesting or hard to achieve, there’s plenty of ways of achieving durable storage. The hard part is doing durable storage while also solving problems like query speed, and concurrency control.
- Guvante 3y agoIt depends on what you mean by durable. Claiming that persistence to disk is trivial when compared to returned values is a stretch IMHO. Modern DBs still have bugs where data returned is different than permanently persisted leading to inconsistency errors. And that is ignoring performance queries that don't require any guarantees.
- avianlyric 3y agoUnless you’re writing directly to a flat file, and basically storing a direct representation of your data on disk, as it exists in your application. Then your DB is doing something to improve the performance of your queries, whether that indexes, or other clever on-disk structures, it exists only to improve query performance.