Skip to content

I build and deploy applications, including the infrastructure behind them.

Here are three projects I've built and deployed. Each one includes its architecture, the decisions I made and why, and the problems I hit along the way.

Role
Cloud / DevOps
Location
India
Status
Open to work

A decision

Every project here is written up like this.

This one is from Stranger Club. It's the part of that system where the order of database writes actually matters, because getting it wrong means two players end up in the same slot.

02

Concurrency: BEGIN IMMEDIATE on capacity-sensitive writes

Decision
Registering a player, confirming a payment, and promoting a waitlisted player each open their transaction with BEGIN IMMEDIATE, taking SQLite's write lock up front instead of discovering a conflict after the fact.
Reason
Without it, two players could both be confirmed into the same last open slot if their requests landed close together.
Tradeoff
This has nothing to do with performance. It's the one place in the system where getting the write order right is what stops the match from being oversold.
Fig. 01: Where the write lock is taken

Architecture diagram with 8 layers. Clients: Player (no account) and Organiser (session and CSRF). These connect to API surface: Public API and Protected API. These connect to Application: FastAPI. This connects to Domain services: Events, Registrations and Payments. These connect to Persistence: SQLite (BEGIN IMMEDIATE on capacity-sensitive writes). This connects to Live updates: Domain state change. This connects to Transport: SSE. This connects to Clients: Connected browser tabs.

And when it went wrong / Self-Service Deployment Portal

Not supported URL scheme http+docker

Cause
Docker SDK for Python incompatible with the host Docker daemon across environments.
Fix
Replaced all container operations with direct Docker CLI invocations via subprocess.
Lesson
The CLI, wrapped carefully, turned out more portable and easier to debug than the official SDK.

password cannot be longer than 72 bytes

Cause
passlib's bcrypt backend enforcing a length limit unexpectedly.
Fix
Dropped passlib, hashed passwords directly with the bcrypt library.
Lesson
Even a wrapper around something as simple as bcrypt can introduce its own bug.

unknown flag --detach on docker create

Cause
Incorrect assumption about which Docker CLI subcommand accepts which flags.
Fix
Switched to docker run --detach.
Lesson
CLI-wrapping needs exact command shapes. Nothing catches a wrong flag before runtime.

Contact

I'm open to work in cloud, DevOps, or backend roles.

I'm based in India. The project write-ups above go into more detail than a CV would.