architecture – Page 30 – Türker Yıldırım

A composable that registers its own onUnmounted

NoteOctober 28, 20212 min read

Cleanup belongs beside the thing it cleans up, and a composable can register lifecycle hooks because it runs inside the component’s setup scope. A mixin could register hooks…

A module with too many variables is a copy

NoteOctober 25, 20212 min read

A module exposing every attribute of the resources it wraps has not abstracted anything — it is the same configuration with an extra indirection. The test is whether…

The report that should have been a materialised view

Deep diveOctober 21, 202110 min read

MySQL has no materialised views and the report needs one anyway. A summary table, a watermark, and the backdated edit that breaks both.

The retry that made the outage longer

Deep diveOctober 21, 202116 min read

A dependency recovered and went straight back down. Every client retrying at once, in lockstep, is a load test nobody scheduled.

A GitHub Actions workflow that other repositories can call

Deep diveOctober 6, 202110 min read

Eleven repositories with the same ninety-line workflow and eleven copies drifting. A fix applied to four of them.

A read model is allowed to be denormalised and stale

NoteOctober 5, 20212 min read

A model shaped for writing is normalised and a model shaped for reading is not, and insisting on one model means one of the two is wrong. The…

provide/inject is not a store and should not become one

NoteSeptember 24, 20212 min read

Provide and inject pass a value down a component tree without prop drilling, and they hide the dependency from everything that reads the component in isolation. The string…

A migration that ran for four hours on a table nobody could lock

Deep diveSeptember 23, 202114 min read

An ALTER on forty million rows and a maintenance window nobody would approve. Online DDL is online until it is not.

Testing what happens when the third party is down

Deep diveSeptember 22, 202110 min read

Every test mocks a 200 and production returned a 502 with an HTML body. The happy path is the only path with coverage.

Problem Details, and an error format that is not invented here

NoteSeptember 16, 20212 min read

Every API invents an error envelope, and RFC 7807 is a perfectly good one that client libraries already understand. type is the field a client should branch on…