4 ms·
Still, why the need to be transactional? An eventually consistent delete seems fine here.
by the_reformation 6y ago
Still, why the need to be transactional? An eventually consistent delete seems fine here.
- danenania 6y agoMaybe it is, or maybe some of the rows are involved in a security check. Or could cause race conditions if out of sync. Or otherwise need immediate read-after-write consistency. And eventually consistent isn't the worst case scenario. Being unable to rollback correctly from an error could mean you'll never end up in a consistent state... that's a lot worse than "eventually".