Aurora DSQL: The Adjudicator
The article discusses the capabilities of Aurora DSQL, particularly its handling of write-write conflicts and the absence of features like foreign keys and SERIALIZABLE. It explains how DSQL can maintain referential integrity by rejecting transactions that would violate it, even in concurrent scenarios. The piece also touches on the complexity of implementing these features and the role of the Adjudicator in managing transaction integrity.
- ▪Aurora DSQL can handle write-write conflict detection but lacks support for foreign keys and SERIALIZABLE isolation.
- ▪The system can reject transactions that attempt to delete accounts involved in ongoing transactions to maintain referential integrity.
- ▪The Adjudicator plays a crucial role in ensuring that transactions do not violate integrity constraints, even in concurrent operations.
Opening excerpt (first ~120 words) tap to expand
The Adjudicator is not constrained to only offering write-write conflict detection. Let’s talk about two features that DSQL doesn’t currently offer: foreign keys and SERIALIZABLE. Every now and then a customer will ask us if our architecture makes this kind of feature hard or even impossible. Nope! It’s really quite simple, and by far the least difficult part of this system. Let’s extend our banking example. We might want to maintain an audit table of all debit-credits: -- as before: do the payment INSERT INTO audit (payer_id, payee_id, amount) VALUES (1, 2, 100); If you wanted to ensure referential integrity then you’d want DSQL to reject a subsequent transaction that tried to delete one of the accounts: DELETE FROM accounts WHERE id = 1; NOTE: If this delete was run concurrently with…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Marc-bowes.
Discussion
0 commentsMore from Marc-bowes
