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.
[ Parent
| on HN ]
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.