Grokking the System Design Interview, Volume II
Vote

0% completed

​

Gmail: Requirements

Step 2: Clarify and Define Requirements

With those six entities named, we can pin down what the service actually has to do. The requirements fall into two groups. Functional requirements say what the service must do. Non-functional requirements say how well it must do it.

Functional requirements

  1. Email composition and delivery. Users send and receive email reliably, from a web client or a mobile app. Sending uses SMTP, the Simple Mail Transfer Protocol. Reading uses IMAP or POP3, the two standard protocols for pulling mail off a server. Both support rich text, reply, and forward

.....

.....

.....

Like the course? Get enrolled and start learning!

Reading Progress

0%

Vote for new content