thatqagirl·1d agoRead Replicas — When Your Database Says Something Different From What You Just SavedYou update your profile, see the success message, and immediately open the page again.
thatqagirl·3d agoBulkheads — Why One Overloaded Service Shouldn’t Sink EverythingImagine you’re on a ship.
thatqagirl·5d agoCache Stampede — When One Expired Key Takes Down Your DatabaseThere’s something strange about performance bugs.
thatqagirl·Nov 8Cache Invalidation — When Your Application Keeps Showing Yesterday’s DataSome bugs are frustrating because the application appears to be working perfectly.
thatqagirl·Nov 6The Saga Pattern — When One Transaction Spans Multiple ServicesI’ve always found it interesting how something that looks like one simple operation to a user can involve several services behind the…
thatqagirl·Nov 4Optimistic Locking — When Two Users Edit the Same RecordHere’s a situation that seems harmless until it starts causing real problems.
thatqagirl·Nov 1The Outbox Pattern — When Your Database Saves the Order but Your Event Never SendsI’ve always found it interesting that a system can successfully save something in the database and still fail to tell the rest of the…
thatqagirl·Oct 30Write Skew — When Every Transaction Passes but the Data Becomes WrongSome database bugs are surprisingly difficult to spot because every transaction can look correct on its own.
thatqagirl·Oct 28Fencing Tokens — When the Old Leader Doesn’t Know It’s Been ReplacedOne thing I find fascinating about distributed systems is that a service can lose authority without realizing it.
thatqagirl·Oct 25Split-Brain in Distributed Systems — When Two Nodes Both Think They’re in ChargeOne of the more unsettling problems in distributed systems is when two parts of the same system believe they are the one in control.
