Cracking the Dropbox / Google Drive System Design Interview Part 2 of 2

No video

Cracking the Dropbox / Google Drive System Design Interview Part 2 of 2

Рет қаралды 4,916

Күн бұрын

Check out part 1 of this two-part series: • Cracking the Dropbox /...
This week, Liz completes a two-part series on how to approach designing a file upload and sharing system such as Dropbox or Google Drive in a system design interview. In this video, Liz covers the different types of compression strategies for file uploads, the sync engine, and how files are stored at Dropbox.
The Challenge:
Design a system such as Dropbox or Google Docs in which a user can store their data on remote servers in the cloud. The remote servers should store files durably and securely, and these files should be accessible anywhere with an Internet connection. The users should be able to make changes to files locally and have the changes be automatically reflected in the cloud and on other clients.
Video Overview:
2:18 The problem
4:04 The sync engine
5:12 Unique challenges at Dropbox
10:00 How changes are reconciled
14:45 When to rewrite your code
19:00 Classic sync to Nucleus
27:08 Huffman encoding
35:00 Magic pocket storage system
38:40 Data model
40:21 Architecture
43:47 Common operations
If you have any recommendations for videos you’d like to see, please comment below.
Reference Links:
* Scaling Dropbox Lecture at Stanford -
• How We've Scaled Dropbox
*Dropbox System Design Article
systemdesignpr...
*Magic Pocket - file content storage
dropbox.tech/i...
*Dropbox Architecture Overview
www.dropbox.co...
Additional Resources:
* Practice hundreds of real coding challenges at coderbyte.com/
* Need more practice? Check out our channel for more videos on preparing for a coding interview / coderbytedevelopers

Пікірлер: 8

@mohajeramir Жыл бұрын

The Huffman encoding blew my mind.

@gitanshgarg1997 2 жыл бұрын

Both parts were awesome. Thank you.

@JB-tq1ly 3 жыл бұрын

great videos as usual !

@aadityagupta250 2 жыл бұрын

Great video! Thanks a lot.

@lilatunes 3 жыл бұрын

these are excellent! Thank you

@johnmok2950 2 жыл бұрын

you are amazing

@totsubo2000 2 жыл бұрын

Quick Question: 1. At 13.35 you say that Nucleus just applies whatever change occurred first. So what does the second user see when they come online? Does the system let them know that their change was not applied? Feedback: Very interesting second part but really not something that I'd expect to be useful on an actual system design interview.

@adithyasama7558 2 жыл бұрын

I get that you are explaining the system. But it would have been better if you talk about a problem and then explained the solution, the dropbox guys came up with, or at least a deeper comparison about how a certain thing was being done before and how it's being done now. The whole section about blocks, volumes and OSD was too unlinked. I mean why is all this complexity there, why is there a need for so many levels of abstraction between the actual block and OSD. The research is in-depth but, it would be hard to reuse this information anywhere else, the first part was better, where there is a clear problem-solution linking. But got lost on this one.