[00:02] about scaling rights beyond what a new database, sharding, or queues will handle, staff-level candidates will change the shape of the problem instead of just absorbing it. How do you do this? One way is batching. Most ways of
[00:16] scaling rights just take the rights as they come and find somewhere to put them. This one's different. It makes fewer, bigger rights. Databases process a batch way more efficiently than the same rights one at a time. This relates
[00:30] to how operating systems and hardware function. Picture a viral post getting liked thousands of times a second, each with a separate right. Instead of hammering the database, put a like batcher in front of it. It watches a
[00:43] 1-minute window, tabulates likes per post, and writes the totals. A post gets 100 likes in that window, you went from 100 rights to one. But this only helps if you actually get multiple events per key per window. If
[00:57] you get one like an hour, batching buys you nothing. This works at the extreme. A celebrity post with a million live viewers all commenting and liking at each viewer. You add a layer of processors that
[01:13] aggregate on the way in and broadcast nodes that fan out on the way out. Now, each node is writing to 100 times less destinations. Want to hear more about how to scale rights in system design interviews? View
[01:27] the whole pattern breakdown on our website hellointerview.com.