notexOPENOverview
Notex/Systems/Step 1 - Understand the problem and establish design scope
08.02LESSON 02 OF 13 · 1 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

System design interview questions are intentionally left open-ended. To design a well-crafted system, it is critical to ask clarification questions.

Candidate: Can you give an example of how a URL shortener work? Interviewer: Assume URL https://www.systeminterview.com/q=chatsystem&c=loggedin&v=v3&l=long is the original URL. Your service creates an alias with shorter length: https://tinyurl.com/ y7keocwj. If you click the alias, it redirects you to the original URL.

Candidate: What is the traffic volume? Interviewer: 100 million URLs are generated per day.

Candidate: How long is the shortened URL? Interviewer: As short as possible.

Candidate: What characters are allowed in the shortened URL? Interviewer: Shortened URL can be a combination of numbers (0-9) and characters (a-z, A- Z).

Candidate: Can shortened URLs be deleted or updated? Interviewer: For simplicity, let us assume shortened URLs cannot be deleted or updated.

Here are the basic use cases:

1.URL shortening: given a long URL => return a much shorter URL 2.URL redirecting: given a shorter URL => redirect to the original URL 3.High availability, scalability, and fault tolerance considerations

Progress is saved on this device.
KEEP EXPLORING

One note leads to another.

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