Open to senior backend, payments and platform engineering roles.Get in touch
Saravana Thiyagarajan
Resume
Case study · Aura Gold™ · Dec 2025 – Sep 2026

A payments ledger that can't afford to be wrong.

How I designed the system of record for customer balances on a Go payment platform serving 1.8M+ users at 300+ TPS.

All projects
Senior Backend EngineerGoAWS SNS/SQSPostgreSQL
01 · Problem

Every balance has to be provable.

A fintech serving 1.8M+ users needed a payment platform whose record of customer balances could be trusted completely, while payments flowed at 300+ transactions per second.

02 · Constraints

Three things that could not be traded away.

Correctness

Postings are atomic. A payment is recorded in full or not at all.

Idempotency

A message delivered twice must not move money twice.

Auditability

Any balance can be reconstructed for any moment, with a full trail.

03 · Design

An immutable double-entry ledger behind an event-driven workflow.

Double-entry ledger

The ledger is immutable and is the system of record for customer balances. It supports atomic multi-entry postings, reversals, reconciliation, a full audit trail and point-in-time balance reconstruction.

Event flow on SNS and SQS

Payment workflows are event-driven on AWS SNS/SQS and PostgreSQL. Consumers are idempotent, which gives exactly-once business semantics.

Modular workflow engine

Each payment moves through the same stages: validation, pricing, ledger posting, notifications and events.

04 · Outcomes

In production, at scale.

I owned the architecture and delivery, led architecture reviews and production releases, and set backend engineering standards.

1.8M+
users served by the platform
300+ TPS
sustained with strict transactional reliability

Hiring for payments or platform engineering?

Open to senior backend, payments and platform engineering roles. Send a message and I will reply with my resume.