Re:Post-incident review on the Atlassian April 2022 outage
by mdavidn on Saturday April 30, 2022 @06:09PM
(#31219879)
This is similar to SQL checkpoints in that a rollback is all or nothing. It wouldn’t be segmented by tenant unless the each tenant has its own transactors.
Re:Post-incident review on the Atlassian April 2022 outage
by eyelidlessness on Saturday April 30, 2022 @07:40PM
(#31220568)
The difference is that, unless you’re using a SQL database with direct/extended support for write-once immutability or a data model designed for it, once the transaction exits every successful committed change is ~final.
A write-once immutability design (whether in the DB itself, or an extension, or a userspace implementation) lets you reconsider and rework mistakes after they’re committed, not unlike how you might do with git rebase etc.
Re:Post-incident review on the Atlassian April 2022 outage
by yawaramin on Saturday April 30, 2022 @10:26PM
(#31221564)
That would be difficult to use given requirements like GDPR's user data deletion.
Re:Post-incident review on the Atlassian April 2022 outage
by closeparen on Sunday May 01, 2022 @07:01PM
(#31229578)
Real world immutable systems usually support the eventual garbage collection of soft-deleted or superseded records. No one actually wants disk usage to grow unbounded forever. It just means you are not going to support "overwrite immediately" semantics in ordinary application code paths.
Datomic describes its capability here: https://docs.datomic.com/on-prem/reference/excision.html
When new data is written, the entire block is copied and rewritten rather than changing the data in-place.