BinaryBox

BinaryBox

Home
Engineering Mindset
System Design
Deep Dive
About

System Design

Deep Dive - What it actually cost to Scale to 1 Million Requests per Second
1,000,000 Requests Per Second (RPS) on a single instance. The result? We hit it. But the bottleneck wasn’t the code logic. It wasn’t the database. It…
 • Ashok Vishwakarma
Thought - The Anatomy of a True Microservice
A true microservice architecture is not defined by the size of the container or the framework you use. It is defined by discipline.
 • Ashok Vishwakarma
Deep Dive - Your Microservices are Actually a Distributed Monolith
You have taken all the complexity of a single codebase and added the two things that kill performance Network Latency and Serialization Costs.
 • Ashok Vishwakarma
Deep Dive - Caching
To understand caching as a technology you must look at the physical materials involved. Not all memory is created equal.
 • Ashok Vishwakarma
Deep Dive - The Load Balancer
To truly understand load balancing, we must move past the surface level of “distributing requests” and look at the Black Box of packet encapsulation.
 • Ashok Vishwakarma
System Design - Books You Must Read
Now that you understand the core concepts the next natural step is to deepen your knowledge with foundational reading.
 • Ashok Vishwakarma
System Design - Event Driven and Asynchronous Design
Synchronous design works perfectly for simple systems but it often fails at massive scale.
 • Ashok Vishwakarma
System Design - How Instagram Delivers Reels Instantly (Case Study)
The most crucial step in the feed process is not video delivery it is the ranking and selection. A slow recommendation engine means the user stops…
 • Ashok Vishwakarma
System Design - How Netflix Streams to Millions Globally (Case Study)
To serve millions of users across 190 countries streaming at different qualities all at the same time requires a truly distributed and robust system.
 • Ashok Vishwakarma
System Design - How JioHotstar Handles 100 Million Concurrent Viewers (Case Study)
In live sports 100 million users hit the system concurrently. If you have only 1000 servers each server would need to handle 100,000 connections
 • Ashok Vishwakarma
System Design - How X (Formerly Twitter) Notifies Millions in Seconds (Case Study)
It exposes the core trade offs every designer must face how to handle massive scale while remaining fast and reliable.
 • Ashok Vishwakarma
System Design - Consistency vs Availability
The CAP Theorem dictates that in a distributed system you can only ever have two of three core properties.
 • Ashok Vishwakarma
© 2026 Ashok Vishwakarma · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture