Skip to content
Ali Akbari
Menu

Backend

Hardening the money paths of a live game

Implementedenvironment:DeployedOwn productSelf-reported · private sourcefluxa-money-path-hardening

Claim

Reviewed and fixed the money and scale-out paths of Fluxa's TypeScript (Fastify) backend in 17 commits: every balance change writes a ledger entry in the same transaction, deposit and payment confirmation use a compare-and-set so concurrent confirms cannot double-credit, N+1 queries, missing timeouts, unbounded reads and missing indexes are fixed, and games fail closed when Redis is unavailable.

Status

implemented
Capped at Implemented: the code, tests and records are private, so this is self-reported and cannot be verified publicly.
deployed
Running in a real, reachable environment I operate.
venture
Products I own and built. The source is private, so these claims are self-reported.

Source

A product I own. Its repositories are private and cannot be published. So this claim is self-reported: it stops at Implemented and links to no artifacts.

Limitations

  • The fixes were not load-tested by me; the repository's k6 scripts are the other engineer's and their results are not recorded.
  • Built with one other engineer; about a third of the commits are mine.
  • Source code: private repository.

Appears in

Related claims

Implementedenvironment:DeployedSelf-reported · private source

Historical market-data pipeline

Built Fluxa's historical candle pipeline: a BullMQ job queue that downloads Dukascopy data in monthly chunks, inserts idempotently, resumes from its last checkpoint after a retry, can be cancelled, and runs in a separate worker process so it never blocks the live price stream.

Data systemsOwn product · no public artifactsEvidence