Designing a payment system that never loses a cent
Payments are where "mostly works" is not good enough, because a duplicate charge or a lost transfer is a real person's money. This is a look at idempotency, the ledger, and the state machine that keep money correct under failure.
Written by
AI engineering, agentic memory, machine learning, and system design at scale.
I work on AI systems and the infrastructure they actually run on: agentic architectures, memory for agents, retrieval, and the graph and data layers that keep model output grounded in something real. Formerly at Neo4j. I also write and teach the systems side that most AI content skips, from distributed systems and databases to the design decisions that decide whether a model ever reaches production. I run Total Technology Zonne on YouTube and I am building systemdesign.academy, an interactive course on system design, machine learning, and AI engineering, covering the parts most tutorials leave as an exercise for the reader. Mock interviews and prep packs: topmate.io/roni
Responses
Markdown supported · ⌘↵ to post
No responses yet.