notexOPENOverview
Notex/Systems/Step 1 - Understand the problem and establish design scope
15.02LESSON 02 OF 18 · 2 MIN READ

Step 1 - Understand the problem and establish design scope

Always free to read
SECTION VIDEOStep 1 - Understand the problem and establish design scope

Video coming soon. Start with the reading below.

COMING SOON

Designing a Google drive is a big project, so it is important to ask questions to narrow down the scope.

Candidate: What are the most important features? Interviewer: Upload and download files, file sync, and notifications.

Candidate: Is this a mobile app, a web app, or both? Interviewer: Both.

Candidate: What are the supported file formats? Interviewer: Any file type.

Candidate: Do files need to be encrypted? Interview: Yes, files in the storage must be encrypted.

Candidate: Is there a file size limit? Interview: Yes, files must be 10 GB or smaller.

Candidate: How many users does the product have? Interviewer: 10M DAU.

In this chapter, we focus on the following features:

  • Add files. The easiest way to add a file is to drag and drop a file into Google drive.
  • Download files.
  • Sync files across multiple devices. When a file is added to one device, it is automatically synced to other devices.
  • See file revisions.
  • Share files with your friends, family, and coworkers
  • Send a notification when a file is edited, deleted, or shared with you.

Features not discussed in this chapter include:

  • Google doc editing and collaboration. Google doc allows multiple people to edit the same document simultaneously. This is out of our design scope.

Other than clarifying requirements, it is important to understand non-functional requirements:

  • Reliability. Reliability is extremely important for a storage system. Data loss is unacceptable.
  • Fast sync speed. If file sync takes too much time, users will become impatient and abandon the product.
  • Bandwidth usage. If a product takes a lot of unnecessary network bandwidth, users will be unhappy, especially when they are on a mobile data plan.
  • Scalability. The system should be able to handle high volumes of traffic.
  • High availability. Users should still be able to use the system when some servers are offline, slowed down, or have unexpected network errors.
Progress is saved on this device.
KEEP EXPLORING

One note leads to another.

Back to the library →
⌕
Search across the entire library ⌘ K