- October 9, 2026A concurrency anomaly where decisions from shared reads lead to conflicting updates on different records.
- October 9, 2026A pattern that commits business changes and pending messages together, then publishes the messages asynchronously.
- October 9, 2026A pattern that atomically records message-processing receipts with business changes to handle duplicate deliveries.
- October 9, 2026Transaction consistency that provides both a valid serial execution order and real-time ordering.
- October 9, 2026Transaction isolation based on consistent snapshots and write-conflict checks, which can still permit write skew.
- October 9, 2026A concurrency-control technique that detects unsafe snapshot-transaction dependencies to provide serializable execution.
- October 9, 2026An anomaly in which related reads reflect incompatible database states and produce an inconsistent combined view.
- October 9, 2026A concurrency anomaly where a repeated query returns a changed set of rows matching its search condition.
- October 9, 2026An anomaly where rereading a row in one transaction reveals a concurrent committed change or deletion.
- October 9, 2026An anomaly where an update overwrites a concurrent change, causing that change to disappear.
- October 9, 2026A read of another transaction's uncommitted data, which may later be rolled back.
