0% found this document useful (0 votes)
12 views1 page

System Design Flow Overview

The document outlines a systematic approach to system design, starting with understanding the problem and defining use cases. It emphasizes the importance of considering constraints such as request rates and data storage needs. The final step involves creating an abstract design that includes service layers, infrastructure, and addressing potential bottlenecks.

Uploaded by

Natsu Dragoneel
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views1 page

System Design Flow Overview

The document outlines a systematic approach to system design, starting with understanding the problem and defining use cases. It emphasizes the importance of considering constraints such as request rates and data storage needs. The final step involves creating an abstract design that includes service layers, infrastructure, and addressing potential bottlenecks.

Uploaded by

Natsu Dragoneel
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

System

Design Flow

1. Understand the problem and scope:
- define the use cases, with interviewer's help
- suggest additional features
- remove items that interviewer deems out of scope
- assume high availability is required, add as a use case
2. Think about constraints:
- ask how many requests per month
- ask how many requests per second (they may volunteer it or
make you do the math)
- estimate reads vs. writes percentage
- keep 80/20 rule in mind when estimating
- how much data written per second
- total storage required over 5 years
- how much data read per second
3. Abstract design:
- layers (service, data, caching)
- infrastructure: load balancing, messaging
- rough overview of any key algorithm that drives the service
- consider bottlenecks and determine solutions

You might also like