Eventual Consistency Explained
Your data disagreeing with itself isn't a bug - it's a trade-off. What eventual consistency actually guarantees, where you're already relying on it, and how to design for it instead of getting bitten by it.
REST APIs in Production: Pagination, HATEOAS, and the Patterns That Actually Matter (Part 3 of 3)
Part 3 of a REST API design series: pagination, HATEOAS, filtering and search, rate limiting, idempotency keys, and the practices that separate a demo API from a production one.
REST API Design: Resources, Versioning, and Auth That Hold Up (Part 2 of 3)
Part 2 of a REST API design series: naming resources so they don't need a manual, versioning without breaking clients, choosing an auth pattern, and structuring errors.
REST API Design: The Constraints and HTTP Semantics Everyone Skips (Part 1 of 3)
Part 1 of a REST API design series: what REST actually is, Fielding's six constraints, and the HTTP methods and status codes most APIs get subtly wrong.
Load Shedding: Dropping Requests to Save Your System
Load shedding is the deliberate act of dropping requests to protect your system under overload - and most .NET teams don't have it.
When Business Processes Outlive Your Request
A practical guide to designing long-running business processes with the Saga pattern - covering orchestration vs choreography, compensating transactions, timeouts, and observability.
Keep Your Claude Code Agents Out of the Team's Repo
How to keep Claude Code agents and skills out of shared repos using a dedicated config repo and symlinks.
Your Database Can't Read. Vector Databases Can.
What vector databases are, how they work, and when you actually need one - versus when pgvector is enough.
Hi! Welcome to my blog
Join my newsletter
Distributed systems, .NET, and the tools reshaping how we build them - the trade-offs that don't make it into the docs.
Let's connect
See it on dometrain
See it on dometrain
See it on dometrain
See it on Amazon