I build systems that don't lose your money — ledgers, wallets, and APIs that stay up at 3am.
Currently obsessing over microservices, Saga patterns, and making Go services that scale without drama.
Backend:
Frontend:
Databases:
Messaging & Caching:
Infrastructure:
Also familiar with:
Currently exploring:
Go → Distributed Systems → Microservices → Kubernetes → Cloud
building, learning, contributing, and breaking things along the way.
Currently exploring: NixOS and declarative system configuration — rethinking how I set up and reproduce dev environments, one
.nixfile at a time. Also dipping into open-source contributions along the way.
I contribute to open-source projects when I can.
A production-grade backend system for ticketing, wallets, and real-time analytics — built to handle money correctly, every time.
What makes it interesting:
- Wallet ledger with optimistic locking to prevent race conditions on concurrent balance updates — no double-spends, no lost writes
- Ticketing engine handling inventory, holds, and purchase flows under contention
- Analytics pipeline for real-time event and transaction insights
- Internal services communicate over REST APIs, with Redis for caching and Postgres as the source of truth
> process aswin.service exited with code 0 — see you in the next commit 🫡