Articles and posts I’ve written on engineering, systems, and building things. I also post on LinkedIn.
Why storing raw files in PostgreSQL (TOAST) hurt performance — and how moving binaries to S3 and keeping only metadata in Postgres simplified the architecture and improved latency.
Building a scalable file-sharing platform: Bloom filters for duplicate detection, S3 pre-signed URLs, Elasticsearch for full-text search, token-based sharing, and JWT auth.
How NAT lets multiple devices on a private network share a single public IP when going online — and why it matters for conserving addresses and hiding internal network structure.
Why every engineer should invest in system design before writing code: understanding the problem, weighing approaches, and choosing solutions by trade-offs. Launch of BashCraft System Design — from foundations to real systems like UPI, Tinder, and live commentary.
A deep dive into relational databases: why they matter, how they work, and ACID properties for data consistency, reliability, and integrity.
Why chasing roadmaps and syllabi can kill curiosity — and why most breakthroughs come from going off the beaten path instead of sticking to the “right” track.
How load balancing works and how it can help prevent meltdowns like the Coldplay ticketing crash — keeping systems reliable when traffic surges.
Torrent file structure, bencoding, piece hashes, and building the data structures for a BitTorrent client in Go.
Why BitTorrent, P2P vs client-server, hybrid P2P, .torrent files, and SHA-1 hashing — building a torrent client in Go.
Pieces, tracker, seeders, leechers — how the BitTorrent architecture works and how peers find each other.
Round-robin load balancing in Go with health checks, reverse proxy, and skipping unhealthy backends. Repo: GoLB.
How UPI works — NPCI, virtual payment addresses, authentication, routing, and how India’s payment system handles scale.
What webhooks are, how GitHub uses them for push notifications, and how HTTP callbacks enable event-driven automation.