Cracking the Dropbox / Google Drive System Design Interview Part 2 of 2
Check out part 1 of this two-part series: • Cracking the Dropbox / Google Drive S...
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
https://systemdesignprimer.com/dropbo...
*Magic Pocket - file content storage
https://dropbox.tech/infrastructure/i...
*Dropbox Architecture Overview
https://www.dropbox.com/business/trus...
Additional Resources:
Practice hundreds of real coding challenges at https://coderbyte.com/
Need more practice? Check out our channel for more videos on preparing for a coding interview / coderbytedevelopers