System Design Approach

< 1 min read

System Design Approach

  1. → Step 0:  Understand the Problem before coming to conclusion
  2. → Step 1: Functional Requirements / Minimum viable Product ( MVP)
  3. → Step 2:  Estimation of Scale ( Back of the envelops calculations)
    1. Compute or Storage
    2. Read heavy or Write heavy or Both
  4. → Step 3:  Tradeoffs
    1. C or A
    2. Stateless or Stateful
  5. → Step 4: System Design deep dive
    1. APIs
    2. System Design diagram ( Components)
    3. Data Flow

→ In HLD interview, be the driver. don’t wait for Interviewer to talk
In HLD interview use 5 step process to show breadth and use Step 4 Design Deep

List of Trade off ( For My Reference )

UserClientDNS ServerOn Typing every Key StrokeOn PressEnterGateway + Load balancerGoogle Search Type aheadGoogle Search Engine

Number of People on Earth is 8 B ( Planet Scale)

Peak Query per second for estimation use 2 twice the Av. Query per second ( for Estimations)

Any feature which is essentially a performance Trade off bit it is must have in a MVP it should be part NFR

⚡ Open This Article in DevScribe

Want to save this?
Open in DevScribe

Save this article directly to DevScribe and work on it offline. Edit, annotate, run code examples, and keep all your developer notes in one place.

Leave a Reply

Your email address will not be published. Required fields are marked *

Join the Conversation

Stay Updated with Us

At Devscribe, we promote a lively space for developers to share insights and experiences. Our blog is not just a source of useful articles, but a gathering place where you can connect with like-minded individuals. Join us as we explore trending topics and collaborate on solutions.
Ready to make your voice heard?

By clicking Join Now, you agree to our Terms and Conditions.