About

Hi, I'm Chandra — a software engineer. I design and build distributed systems: event-driven services, data and ML platforms, and the AWS infrastructure that runs them. My hands-on work lives mostly in Go, Python, and TypeScript, and these days most of my time goes into building OrbitShift.

This blog is where I write up the engineering decisions behind shipping software at scale — service boundaries, consistency and failure modes, scaling bottlenecks, and the trade-offs that don't show up in the happy path. The goal is to keep things concrete: the kind of write-up I'd want to find when facing the same decision myself.

Most posts start as something I had to figure out at work: a system that had to handle more load, a service boundary drawn in the wrong place, a design with no obvious right answer. I write them down so the next person — often future me — doesn't have to start from scratch.