SRSreekar Reddyinesreekarreddy.hashnode.dev·Apr 27 · 2 min read⚗️ ACID Properties Explained Like You're 5Guarantees for data reliability Day 123 of 149 👉 Full deep-dive with code examples The Bank Transfer Analogy Transferring money from Account A to B: Subtract the amount from A Add the amount to B What if the power goes out between steps? A lost ...00
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 17 · 38 min readACID Properties Explained: How SQL Databases Guarantee Atomicity, Consistency, Isolation, and DurabilityTLDR: ACID is four orthogonal guarantees that every SQL transaction must provide. Atomicity says all-or-nothing: PostgreSQL implements it via WAL rollback; MySQL InnoDB via undo logs. Consistency says00
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 11 · 38 min readLost Update Explained: When Two Writes Become OneTLDR: A lost update occurs when two concurrent read-modify-write transactions both read the same committed value, both compute a new value from it, and both write back — with the second write silently00
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 11 · 23 min readWrite Skew Explained: The Anomaly That Requires Serializable IsolationTLDR: Write skew is the hardest concurrency anomaly to reason about: two concurrent transactions each read a shared condition, decide they can safely proceed, and then write to different rows. No indi00
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 11 · 26 min readNon-Repeatable Read Explained: When the Same Query Returns Different ResultsTLDR: A non-repeatable read happens when the same SELECT returns different results within a single transaction because a concurrent transaction committed an update between the two reads. Read Committe00
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 11 · 32 min readPhantom Read Explained: When New Rows Appear Mid-TransactionTLDR: A phantom read occurs when a transaction runs the same range query twice and gets a different set of rows — because a concurrent transaction inserted or deleted matching rows and committed in be00
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 11 · 28 min readDirty Write Explained: When Uncommitted Data Gets OverwrittenTLDR: A dirty write occurs when Transaction B overwrites data that Transaction A has written but not yet committed. The result is not a rollback or an error — it is silently inconsistent committed dat10
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 11 · 34 min readRead Skew Explained: Inconsistent Snapshots Across Multiple ObjectsTLDR: Read skew occurs when a transaction reads two logically related objects at different points in time — one before and one after a concurrent transaction commits — producing a view that never exis00
AAAbstract Algorithmsinabstractalgorithms.dev·Apr 11 · 30 min readDirty Read Explained: How Uncommitted Data Corrupts TransactionsTLDR: A dirty read occurs when Transaction B reads data written by Transaction A before A has committed. If A rolls back, B has made decisions on data that — from the database's perspective — never ex00
PPromiseinpromise-security.hashnode.dev·Apr 5 · 6 min readUsing Splunk to Detect Financial Fraud: My Commonwealth Bank Cybersecurity TaskAs part of a virtual cybersecurity experience with Commonwealth Bank, I completed a hands‑on fraud detection task using Splunk. The goal was to analyse a synthetic transaction dataset, build a dashboa00