3 ms·
re: "immutable" database use cases: internet archive : https://archive.org/ 'old' news media :https://mediahistoryproject.org/ perhaps including orwell'
by sargstuff 4y ago
re: "immutable" database use cases:
internet archive : https://archive.org/
'old' news media :https://mediahistoryproject.org/ perhaps including orwell's '1984'
version specific api documentation : https://swagger.io/blog/api-documentation/what-is-api-documentation-and-why-it-matters/
voyager 1 & 2 golden record : https://en.wikipedia.org/wiki/Voyager_Golden_Record
- gregjor 4y agoRight, limited value as I wrote. Most modern database engines support read-only databases, it’s more a configuration than a different kind of database.
- sargstuff 4y agoUmmm... would characterize an immutable database as a more as a specific use case than general application configuration aka write once, read many traditionally for transactional logging/recovery. For concurrent transactions/databases, the immutable stuff does allow for making certain assumptions to improve performance. database management systems typically support/provide front end to multiple/different database engines. As with most things in software world, general situations that allow for customize use case configuration setup, and specific designs/implimentation for specific situations.