Rebuilding the billing flow as events
Why the second version of an event-driven design is usually the simpler one, and the retry question that decided the whole shape.
Related
Keep reading
I built an AI agent that makes our church's Sunday slides
Every week the same few volunteers spent two hours or more chasing sermon slides, copying Bible verses and fixing line breaks. So I built them an agent that does it on Thursday evening, for about seven cents, and still lets a person say no.
Idempotent consumers, without the ceremony
What actually happens when the same message arrives twice, and the smallest set of changes that makes a consumer safe to retry.
Designing a URL shortener
The classic interview system, built small and measured: where the reads go, what the cache is for, and the one decision that made everything else easy.
Next
Something here worth a reply?
If this entry raised a question, or you think I have got something wrong, I would much rather hear it than not.
Get in touch