system-design – Page 8 – Türker Yıldırım

The state file two people wrote to at once

Deep diveJuly 14, 202310 min read

Two pipelines, one state file, and a plan that proposed deleting a database. A lock held by a run cancelled forty minutes earlier.

Container queries, and the component that stopped needing a prop

Deep diveJuly 7, 202310 min read

A card with a variant prop that exists only to describe its width, rendered wrong in a sidebar somebody added last week.

Patterns as a deliverable, and the editor who stopped asking us

Deep diveJune 27, 20239 min read

A request for a new landing page layout, for the ninth time. Every campaign page a developer ticket, for work that is arrangement.

Partitioning by month, and the query that scanned all of them

Deep diveJune 27, 202310 min read

A 400 million row events table and a delete that could not finish. Dropping a partition takes two seconds; getting there takes a schema change.

An error budget, and the deploy freeze we did not need

NoteMay 30, 20232 min read

The policy said a burnt budget triggers a deploy freeze; the budget was burnt by one incident and the freeze would have blocked the fix. A freeze assumes…

The anti-corruption layer we should have written first

Deep diveMay 9, 202310 min read

A supplier who renamed four fields in a minor release, without notice, and twenty-two files touched to accommodate it.

A backup we restored on purpose, every month, forever

Deep diveApril 5, 20238 min read

A backup that had run nightly for four years and had never been restored. The first restore produced a database missing one table.

A read replica, and the six queries that could not use it

Deep diveMarch 16, 202314 min read

A primary at 80% CPU and reports running during the working day. Setting up the replica takes an afternoon; the consistency model takes a month.

Reading a service in another language well enough to file a bug

NoteFebruary 22, 20232 min read

A service owned by somebody else, in a language I do not write, returning the wrong value — and “it is broken” is not a bug report. Reading…

Extracting a module without extracting a service

Deep diveFebruary 3, 202314 min read

A billing module everybody agrees should be separate, a team of four, and 88 classes that reference it. The boundary, drawn in code rather than in conversation.