Optimistic vs Pessimistic Locking
Every payments engineer eventually meets the same enemy: two requests that arrive at almost the same instant, both convinced they are operating on the truth. A...
11 min346Read →
Tagged #backend — Page 3
Structured Logging in .NET
Every incident review I have ever sat through eventually arrives at the same uncomfortable question: what was the system actually doing at the moment it...
11 min792Read →
Designing Idempotent Event Consumers
Every distributed payments platform I have built eventually arrives at the same uncomfortable truth: messages get delivered more than once. Not occasionally,...
12 min485Read →
Retry Logic and Exponential Backoff
Every payment platform I have run eventually develops a relationship with failure. Not the catastrophic kind that wakes you at three in the morning, but the...
11 min676Read →
Feature Flags Done Right
Every engineering team I have led eventually reaches the same uncomfortable moment: a release is ready, the code is merged, and yet nobody is quite willing to...
11 min391Read →
Understanding Eventual Consistency
Every engineer who has built a payments platform eventually runs into the same uncomfortable truth: the moment your system spans more than one database, one...
11 min476Read →
Caching Strategies Every Backend Engineer Should Know
Caching is one of those topics that sounds simple until you ship it. Add a cache, serve a few requests from memory, watch your latency graph drop, and call it...
10 min925Read →
When to Use a Message Queue, and When Not To
Few pieces of infrastructure get reached for as reflexively as the message queue. Somewhere in the lifecycle of every growing system, an engineer looks at a...
12 min1001Read →