Loading home…
I write about what I ship in production: NestJS, AWS, and distributed systems.
Latest article
Who else needs to know once the money has already moved? I asked myself that with the ledger freshly done and no topic running yet. That week I split what happened in the domain from the message Kafka will carry next.
6 articles
Rebuilding a banking core phase by phase — accounts, transfers, ledger, and events with open source NestJS code and articles that explain why, not just how.
View full series →
4 articles
Production NestJS patterns — modular architecture, testing, observability, and AWS from real backends, one article at a time.
View full series →
How do you prove the money moved if the client retries after a timeout? I asked myself that while picturing a balance column and an UPDATE again. That week I wrote movements you never delete
What happens when money stops being a number and becomes a responsibility? I asked myself that looking at amountCents in my POST /transfer draft. That day I wrote Money.
Six boxes on the diagram. Six microservice temptations. I almost fell for it again — until I got that the full map doesn't mean shipping it all in week one, and splitting repos doesn't split the domain
Three seconds on the spinner. Timeout on screen. Did the money move? I reopened my Arkano challenge next to a fintech architecture map — and understood why POST /transfer was never just an endpoint.
A LinkedIn post on fintech architecture, a recent technical challenge, and a decision to rebuild a banking core from scratch — slower this time, to actually learn.
No spam — just a note when I publish something new on backend, cloud, and architecture.
One email when a post goes live. Unsubscribe anytime.