Read-After-Write ConsistencyRead-After-Write (RAW) consistency, also called Read-Your-Writes consistency, means that after a user or client successfully writes data, an immediate read will return that new data or a newer versionOct 4 · 5 min readbotanicalcodersblog.hashnode.dev
Database Deadlocks: When Transactions Get Stuck Waiting for Each OtherA database deadlock happens when multiple transactions are waiting for each other in a way that means none of them can continue. Each transaction may be perfectly valid on its own. The problem comes fOct 4 · 8 min readbotanicalcodersblog.hashnode.dev
Idempotency Is Not the Same as Concurrency ControlIdempotency and concurrency control are distinct backend design guarantees that solve two fundamentally different failure modes in distributed systems. Idempotency ensures that executing the same logiOct 4 · 9 min readbotanicalcodersblog.hashnode.dev
Time of Check to Time of Use (TOCTOU)The pattern: if (balance >= amount) debit() can fail under concurrency because the check and the subsequent debit are separate operations rather than one atomic check-and-act operation. It splits a sSep 29 · 7 min readbotanicalcodersblog.hashnode.dev
Locks, MVCC, Isolation Levels, Atomic Updates, Optimistic and Pessimistic Concurrency; the major tools databases use to control concurrent operations. Managing concurrent operations safely while maintaining performance is a central challenge of database engine design. Database engines achieve this using several core primitives and concurrency controSep 28 · 9 min readbotanicalcodersblog.hashnode.dev