Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4133 pages

Blog

Databases, Servers and Runtime Behaviour, From the Docs

What the defaults of databases, caches and servers do under load and failure, and which choices are hard to undo, read from each project's own documentation.

A database or cache usually works fine until the day its default turns out to mean something different from what you assumed. Two engines can both offer repeatable reads and behave differently when two transactions touch the same row. A cache can be full and refuse writes, or full and quietly delete keys. The notes here take one such behaviour at a time and read what the project's own documentation promises, what it leaves open, and what an application has to do about it.

Everything is taken from the official documentation named under each page's Sources, fetched on the date shown there. These pages explain documented behaviour. They are not benchmarks, and they are not accounts of systems I ran for the page. Versions matter, so check the version of the documentation against the version you run before you change a setting.

Running servers

2026-11-20

SQLite WAL Mode: What It Fixes, What It Costs and Where It Breaks

Turning on SQLite WAL mode stops readers and a writer from waiting on each other, and the choice is written into the database file, so it outlives the connection that made it. It still allows only one writer, it does not work across machines on a network share, and a database that always has a reader open can grow its -wal file without limit.

Read

2026-11-20

Redis maxmemory-policy: Eviction Choices and Their Side Effects

Your redis maxmemory-policy decides what a full Redis does: delete data or refuse writes. The shipped default, noeviction, keeps every key and errors on commands that need memory. The volatile policies only remove keys that carry a TTL and give the same errors when none do. For a plain cache, the Redis docs point to allkeys-lru.

Read

2026-11-20

MySQL vs PostgreSQL Default Isolation Level: What Changes for Your Transactions

The MySQL vs Postgres isolation level gap bites when code moves between them: the same name, REPEATABLE READ, fails in opposite ways. InnoDB uses it by default and lets an UPDATE touch rows its snapshot never showed. PostgreSQL defaults to READ COMMITTED, and its REPEATABLE READ aborts a conflicting write with SQLSTATE 40001 that your code must retry.

Read

2026-11-20

Kubernetes Requests vs Limits: Scheduling, CPU Throttling and OOM Kills

Getting kubernetes requests vs limits wrong shows up as Pods stuck Pending, slow containers or restarts with OOMKilled. Requests are a placement promise the scheduler checks against node capacity. Limits are enforced at runtime: going over the CPU limit only slows a container, while going over the memory limit can get it killed. Together they also fix the QoS class.

Read

Next step

Have a project in mind?

Tell me about it. A discovery call within 48 hours.