Jatin Jain Saraf

Senior Software Engineer · SupraScan Architect

I build the systems that make blockchains queryable. Written from the pager alerts, not the docs — every course module and article here cost an incident first; these are the notes I wish I'd had before it did.

Credentials

Senior Software Engineer, Supra (via CodeZeros)

Lead architect of SupraScan — Supra Blockchain's native explorer and indexer, running PostgreSQL at 20–30 TB scale.

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.

Courses I've written

All courses

PostgreSQL In-DepthFrom First Query to Production Architecture Node.js In-DepthFrom Runtime Basics to High-Throughput Distributed Systems Next.js In-DepthFrom First Route to Production-Grade Architecture Redis In-DepthFrom Runtime Basics to Distributed Architecture at Scale Master JavaScript TestingFrom Unit Tests to End-to-End Mastery Docker In-DepthFrom Container Internals to Production SaaS Deployment Data Structures and Algorithms In-DepthFrom First Principles to Architect-Level Systems Thinking

Recent articles

All articles

How the LRU Cache Actually Works and Why Redis, Browsers, and Postgres All Approximate ItEvery fast system you use eventually has to decide what to throw away. The Least Recently Used policy is the answer nearly all of them land on, here's the two-structure trick that makes it instant, and why Redis, your browser, and Postgres all quietly cheat on the textbook version at scale.Why a Single ALTER TABLE Can Take Down Your Whole DatabaseA routine ALTER TABLE queues behind one slow query — and every SELECT that arrives after it queues too, even though they'd normally run just fine together. This is the PostgreSQL locking mechanic behind some of the ugliest production outages, and the two settings that prevent it.What the PostgreSQL Server Is Actually DoingWhen you run CREATE DATABASE, PostgreSQL creates a directory. When you run INSERT, it writes a row to a file and logs the write for crash safety. When you run SELECT, it reads that file back.Competition Is Inevitable. Cruelty Is OptionalEvery promotion in tech has an invisible downside. When someone becomes a Senior Developer, someone else waits another review cycle. That's the reality of a competitive industry. But success isn't abo Transactions and ACID in Practice: What Every Backend Developer Must KnowThe money left Alice's account. Bob never received it. The server crashed in between. If you don't understand transactions, this is how your application loses data, silently, permanently, with no erro When Judgment Becomes the BottleneckSenior engineers get rewarded for good judgment, until that judgment becomes the thing every decision waits on. Here's how to recognize when you've become the bottleneck, and what to do about it.

Get in touch