π Based in Azerbaijan Β· π¬ EN / AZ / RU / TR
I build distributed systems, payment infrastructure and trading platforms.
Backend-heavy, type-safe, observability-first.
Lately a lot of TypeScript + Postgres/SQLite + event-driven architectures, with detours into Rust and Go for the latency-sensitive bits.
| Project | Architecture & Infrastructure Highlights |
|---|---|
| π QuantTrade Platform | Bank-grade trading infra β saga orchestrator, event-sourced wallet with snapshots, in-memory order book, distributed locking, and circuit breakers. |
| π Ledger Secure Platform | Stripe-Treasury-shaped double-entry payments β 6 microservices, multi-currency, HMAC webhooks, and real-time fraud scoring. |
| π Mercatum | Microservices e-commerce β catalog / inventory / cart / order / payment / search, saga checkout, and FTS5 search. |
| π PaySec | Payment-gateway simulator β 8 methods, 3DS challenges, webhook delivery, and an interactive admin dashboard. |
| π Atlas | Real-time collaborative docs β CRDT, WebSocket sync, AI agent with tool-use, and offline replication. |
π‘ Each one ships with a working seed, an end-to-end smoke test and a README that documents the architecture trade-offs, not just the happy path.
A meaningful slice of my work lives in private repos. The reasons are deliberate, not accidental:
- πΌ Client and contract work: Code I've written under NDA stays where it belongs β with the client. Reach out if you'd like a walk-through on a call.
- π οΈ Work in progress: Some projects are still pre-launch or mid-rewrite. They'll go public when they're ready to be judged on their merits, not their scaffolding.
- βοΈ Personal tooling: Internal scripts, experiments, and notes I run on my own machines. They serve me; they don't need to serve anyone else.
Note
If you want a deeper technical conversation about something you don't see here, send me a message β I'm happy to share specifics directly.
π« Open to interesting backend / distributed-systems work β reach me via GitHub or socials.