I make PostgreSQL work at production scale. Everything here is written from the pager alerts, not the docs: every case study, course module and article cost an incident first, and these are the notes I wish I'd had before it did.
Credentials
Senior Software Engineer, Supra (via CodeZeros)
Architect of SupraScan, Supra Blockchain's native explorer and indexer: 500–1,000 TPS on a PostgreSQL database that grew to 10 TB, now 2.7 TB.
6+ years in production engineering
From enterprise B2B platforms (Rapidops — Kroger, Salesmate CRM) to high-throughput Web3 indexing infrastructure.
Author, In-Depth course series
PostgreSQL, Node.js, Next.js, Redis, Docker, and Data Structures & Algorithms — free, documentation-style courses built from production incidents.
B.E. in Information Technology
Truba Institute of Engineering and Information Technology, Bhopal — 7.76 CGPA.
Case studies
All 12Indexing a Blockchain in Real Time, at ScaleA blockchain never pauses for maintenance. Here's how SupraScan's indexer stays caught up, decomposes every transaction into a dozen relational tables, and survives its own concurrency bugs without losing data.Scaling a Blockchain Database From a Single Partition to 4.6 TBA partition strategy that worked in 2021 became a 10TB liability by 2026. Here's the five-stage evolution that got it back under control, the outage the last stage caused, and the storage arc from 10TB avoided to 4.6TB today.Exact Analytics in 12KB: Hardening a Wallet-Uniqueness SystemHyperLogLog gets you exact distinct-wallet counts at near-zero memory cost. The hard part is not the algorithm, it's keeping it correct under concurrent production writes. Five real bugs, one week, five different ways correctness quietly slips.Concurrency Design Under High TPS: Moving Wallet Counters Off Database TriggersA 3-4 day indexer lag traced back to four wallets and a database trigger. The fix moved counting logic out of the database entirely, and a routine check-with-the-docs step turned up an architectural assumption that had been wrong all along.
Courses I've written
All coursesPostgreSQL In-DepthFrom First Query to Production ArchitectureNode.js In-DepthFrom Runtime Basics to High-Throughput Distributed SystemsNext.js In-DepthFrom First Route to Production-Grade ArchitectureRedis In-DepthFrom Runtime Basics to Distributed Architecture at ScaleMaster JavaScript TestingFrom Unit Tests to End-to-End MasteryDocker In-DepthFrom Container Internals to Production SaaS DeploymentData Structures and Algorithms In-DepthFrom First Principles to Architect-Level Systems ThinkingSystem Design In-DepthFrom the Silicon to the Multi-Region Ledger
Recent articles
All articlesBloom Filter, Reservoir Sampling, HyperLogLog: Three Probabilistic Answers to Three Different QuestionsAll three trade exactness for memory, which is why they get mixed up. A Bloom filter answers "have I seen this wallet?", a reservoir answers "give me a fair sample of the stream", and HyperLogLog answers "how many distinct wallets?". Pick the wrong one and you don't get a slightly worse answer. You get a confident answer to a question you didn't ask.Your Node.js App Never Imports zlib. It Might Still Be Vulnerable to a Brotli RCENode.js patched CVE-2026-111497, a High-severity Brotli decoder flaw, on October 21, 2026. I traced the built-in fetch() through Undici to show how a response reaches that decoder even when your code never imports zlib, and wrote up the checklist for verifying what production actually runs.You Might Not Need a Queue Service: Postgres SKIP LOCKED as a Job QueueBefore adding Redis, BullMQ, or SQS just to distribute background work, look at the database you already run. PostgreSQL's FOR UPDATE SKIP LOCKED lets multiple workers claim different jobs concurrently. Learn how to handle expired leases, retries, MVCC bloat, and notification-based wake-ups, and when a dedicated queue is the better choice.How a B-Tree Really Reads, Inserts, Updates and Deletes (and Where It Fails a Blockchain Indexer)A B-tree is cheap to search and expensive to keep sorted. Here’s what reads, inserts, updates and deletes actually do inside one in PostgreSQL, and how that should decide the index on every table of a blockchain indexer, from wallet history to balances to NFTs.Turning Your Blockchain Indexer Into a Paid API Without Slowing Down Your ExplorerTurning blockchain indexer data into a paid API is easy. Keeping API traffic from slowing your explorer or ingestion is the hard part. This post presents a production architecture using replica pools, read models, finality-aware caching, Redis quotas and per-plan bulkheads.Your Postgres Indexes Can Break Without a Single Line of Code ChangingYou bumped the base image or rebuilt a replica on a newer OS. No deploy, no migration. Then a unique index lets in a duplicate and an indexed lookup misses a row you can see. Here's how collation drift breaks B-tree indexes, how to prove it with amcheck, and the fix order that doesn't silence the only alarm.