Database Transactions in Practice
ACID is not a slogan; it is a specific set of storage mechanisms. This video traces a transaction through the write-ahead log, the lock table, and the undo log, showing how durability, rollback, and isolation are actually implemented, and what each isolation level permits when two transactions touch the same rows.
Topics covered:
- The write-ahead log: how durability actually works
- Undo and redo: rolling back a transaction
- Locks: shared vs exclusive, and deadlock detection
- Isolation levels and the anomalies each one permits
- MVCC: readers that never block writers
- Long transactions: why they hurt and how to shrink them
Related articles
Connection Pools Aren't Free
Pool sizing, exhaustion, idle connections, and the hidden queue — why 'just add a pool' is incomplete advice.
Circuit Breakers and Timeouts: Protecting Services from Cascading Failure
Circuit breaker states — closed, open, half-open — plus timeout budgets and retry limits: the mechanisms that stop cascading failures before they spread.
Caching Strategies at the Service Layer: Redis, Local Cache, and Cache-Aside
Service-layer caching compared: cache-aside, write-through, TTLs, invalidation, stampede control, and Redis vs in-process cache tradeoffs.
More in Backend Engineering
Pagination Strategies
Offset, keyset, and cursor pagination compared by database cost, consistency, and behavior when rows are inserted mid-page.
DetailsCaching for the Service Layer
Service-layer caching done right — cache keys, invalidation, TTLs, and the stampede problem that brings services down.
DetailsWebhooks vs Polling
Webhooks and polling compared at the delivery level — delivery guarantees, retries, and when push is worse than pull.
DetailsRate Limiting Algorithms, Visualized
Token buckets, leaky buckets, and sliding windows compared by memory, precision, and what they do under burst load.
DetailsAPI Idempotency Keys
How idempotency keys work at the storage level — dedupe tables, unique constraints, and making retries safe for clients.
DetailsBackground Job Processing
Queues, workers, and retries — how background jobs actually execute, from enqueue to acknowledgment, and why they fail.
DetailsREST APIs from the Inside
What happens when a REST API processes a request — routing, deserialization, validation, handlers, and response building end to end.
DetailsMessage Queues in Practice
Brokers, producers, and consumers — what a queue does at the protocol level and why it decouples services from availability.
DetailsConnection Pooling Explained
What a connection pool actually does — the handshake cost it hides, checkout and release mechanics, and how pool size changes latency.
DetailsDepth, delivered weekly
One technical dispatch a week — articles and episode notes before they go public.
One technical dispatch per week. No noise.