
Loading home…
Loading home…
Loading blog…
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.

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.

If onboarding a new customer requires deploying a new application or duplicating an entire database, your SaaS architecture probably isn't ready to scale. Learn how to implement multi-tenancy in NestJS in a clean and maintainable way.

If every new feature forces you to modify five different services, you probably have a coupling problem. Learn how Event-Driven Architecture helps decouple modules and scale NestJS applications.