Your Food Is Ready. Your Delivery Partner Isn't.: A 15-minute meal becomes a 45-minute delivery. The system design behind kitchen predictions, dispatch timing, and the promise on your food delivery app.
Behind the Moving Dot: Live Delivery Tracking with Kafka: How would you build Swiggy- or Zomato-style live tracking? Follow a GPS ping through Kafka, ordered processing, a location cache, and WebSockets—and see what happens when the network fails.
Why Your Uber Driver Is Across the Street: The pin looks right. The pickup goes wrong. How GPS uncertainty, stale updates, and road geometry turn a simple ride into a system design problem.
One cache miss, a million queries: How a single expiring cache key can take down your database. The thundering herd explained, with real outages and seven fixes from request coalescing to probabilistic early expiry.
10:00:00 AM — India's daily DDoS: Why IRCTC struggles every morning at Tatkal time. A system design look at synchronized crowds, segment-based seat inventory, payment pile-ups and the bots racing you for a berth.
One line broke the internet: Cloudflare, CrowdStrike, Facebook and AWS were each taken down by a tiny change that shipped everywhere at once. What went wrong, the pattern they share, and how to ship config safely.
Designing Uber, end to end: A detailed system design of a ride-hailing platform, from a driver's GPS ping to the payment captured after the trip, with the trade-offs at every step.
HLS video streaming from scratch with FFmpeg and Java: Turn one MP4 into an adaptive, encrypted, CDN-friendly stream. Bitrate ladders, segment sizes, ABR, AES-128 and a Java pipeline that runs it all, with charts at every step.
From .java to the CPU: how Java code actually runs: Follow a real program from source code to bytecode, class loading, stack frames, JIT compilation and garbage collection—with diagrams and experiments you can run yourself.