Architecture

120 posts filed under Architecture.

Nobody wants to be the one who questions the tool the last person bought before they left.

Postgres handled it fine. Until the agent started issuing thousands of embedding lookups a second.

We changed the questions in the postmortem, and the recurring outage stopped recurring.

Four questions, asked consistently, replaced most of one engineering manager's architecture decisions.

A company at 40 people needs senior data judgment about 2 days a week. Full-time is the wrong container.

Single-cloud is a fine strategy. Unpriced lock-in is a negotiating position, and not yours.

Nobody owned the orders table. Everyone had opinions about it in the incident channel.

Your engineers are already learning AI at work. The only question is whether it's sanctioned.

A 60-person scaleup asked me to design their data mesh. After the readiness check, we kept the central team.

Tech debt gets a backlog and a budget. Leadership debt gets a shrug, and it compounds faster.

Want expert eyes on your data architecture?