Grokking the System Design Interview
Vote

0% completed

​

Designing Dropbox

Every case study in this chapter follows the same seven steps from System Design Interviews: A step by step guide, and builds its design from the components in the System Design Master Template. Keep both open beside you, and try each problem yourself before reading the solution.

Why Cloud Storage?

Dropbox is a cloud file storage service

.....

.....

.....

Like the course? Get enrolled and start learning!
N

nayak.bishwa

· 7 months ago

Just thinking loud, If the User is a celebrity or high profile user or taken some premium service and the user got too much space in any file system and then he/she created 1 directory and put like lot of image or video files lets say data in TB then what would happen? The complete directory will be in one partition.

N

nrnavodit1

· 2 years ago

In the detailed diagram it shows that the metadata is updated first and then it is sent to the synchronizing service but in the text explanation, it’s vice versa… which flow should we consider?

K

knowledgeshop

· 2 years ago

The final diagram has LBs for Metadata Servers but not Block Serveres. I believe its required and the diagram should be corrected.

Show 1 reply
S

sghanish

· 2 years ago

Data Duplication for Fault Tolerance is not discussed in this system design ?

R

Rahul Khandalkar

· 4 years ago

With same idea, can someone explain how to scale 1 server to upload a 20 gb file to 20 server and then scaling up to 10000 server in same data center.

S

Sandeep Kumar

· 4 years ago

Can Memcached be used to store chunks of data? Since, it is a key-value store.

Show 1 reply
W

WZ

· 4 years ago

Question about the message queue. Based on the text, it seems one user can have multiple clients (mobile, pc, web, etc.). And the backend needs to maintain a response queue for each of the clients. Now we have 500M users and 3 devices per user. So we are maintaining 1.5B response message queues. Isn't that quite a big scaling challenge? Also, we can we add a chapter for MQ in the system design basics section?

S

swe

· 4 years ago

how would synchronization work if separate clients make changes to the same file that affect different chunks, but the updated chunks in combination would result in a corrupted file?

Is that possible?

Show 4 replies
S

Surbhi Goel

· 4 years ago

Security section should be explained more. Possible breaches and solutions should be added

Show 1 reply
J

JC Denton

· 5 years ago

I am curious to learn more about how the message queue scales - If users can have multiple devices with many updates queued up for each device, the storage requirements could be quite large?

Show 1 reply

Reading Progress

0%