01Distributed Systems · 2026.03 · 8 min
The log is the truth
Ten services, no shared database, and one append-only record everyone agrees on. Notes on designing an event log you can actually reason about.
Chapter One: The Name
Engineer.
Designer.
Builder.
Software engineer building distributed systems, predictive intelligence, and interfaces built to be remembered.
Contribution field — playable
0000 eaten · length 1 · auto
Arrow keys or WASD to steer · click a square to send it there · 0 squares cleared
Chapter Two: Manifesto
Ibuildtheonespeopleactuallyremember.
Position
Computer Science at IGDTUW. Software engineering at Flipkart, previously Deutsche Telekom Digital Labs. President of the Microsoft Student Chapter.
Preoccupation
Distributed systems, event logs, and the quiet discipline of observability — the parts of software nobody photographs.
Instruments
JavaPythonC++SQLSpring BootApache KafkaMicroservicesDockerRedisMySQLReactTailwind CSSScikit-LearnFastAPI
Chapter Three
Three systems, documented as they were built.
Distributed Systems
Ten services. One conversation.
A distributed recommendation platform built as an event-driven organism — ten Spring Boot services speaking asynchronously through Kafka, each one deaf to the others except through the log.
Predictive Intelligence
The machine tells you before it breaks.
An end-to-end predictive maintenance platform: sensor data in, failure probability out, with cost-sensitive learning that treats a missed failure as the expensive mistake it actually is.
Interface Systems
Legacy systems, rewritten as calm.
A full academic management portal built against the usability failures of legacy university software — modular components, clean data surfaces, and workflows that survive a bad network.
Chapter Four: Record
Software Engineer Intern · Bengaluru
President · IGDTUW
Software Engineer Intern · Gurugram
B.Tech Computer Science · CGPA 8.42
Top 200 of 27,000+ — Flipkart Girls Wanna Code 7.0
Semi-Finalist — EY Techathon 6.0
98.5% template extraction accuracy — log analytics platform, Flipkart
Chapter Five: Journal
04 entries · hover to read
01Distributed Systems · 2026.03 · 8 min
Ten services, no shared database, and one append-only record everyone agrees on. Notes on designing an event log you can actually reason about.
02Design · 2026.01 · 6 min
Every screen makes a claim about what matters. On drawing before building, and why the paper stage is the cheapest place to be wrong.
03Performance · 2025.11 · 11 min
Tail latency is a design decision, not an accident. How to spend milliseconds deliberately across a request path.
04Practice · 2025.09 · 5 min
Running a student chapter taught me more about architecture than any design doc. On explaining systems to a room that will ask why.
Chapter Six: Dispatches
Shipped a change that cut p99 on the ranking path by a third. The fix wasn't clever — it was deleting a synchronous call nobody remembered adding.
Notes from building an event-driven platform across ten services: contracts first, dashboards second, opinions last.
Spoke to the Microsoft Student Chapter about observability — the part of software nobody photographs, and the first thing you miss at 3am.
Marginalia — Fun Facts
12 entriesThink you know me from my code? Think again.

Before the keyboard
I did competitive gymnastics for eight years through DDA Sports under the Delhi Government, right up until 2019. Balance beams teach you more about debugging than most tutorials do.
Chapter Seven: Correspondence
Delhi, India