Fintech9 min min read
Designing idempotent payment APIs that survive retries
Idempotency keys, deterministic state machines, and reconciliation as a first-class concern.

Insights
Practical writing on the systems we build — architecture, infrastructure, fintech, and security.
Idempotency keys, deterministic state machines, and reconciliation as a first-class concern.
What we've learned from running field operations in environments where connectivity is the exception.
Replication, PITR, vacuum, observability — the unglamorous work that keeps your database boring.
Why the threat models that actually protect systems are the ones updated at PR time — not at audit time.
Cost guardrails before code, tagged resources, and the quiet 20-30% bill reductions that come with them.
The boring parts of retrieval-augmented generation: chunking, hybrid search, and the eval suite that decides everything.