System design template as published on leetcode
|
Security
|
Capacity
|
|
Compatibility (OS, etc)
|
reliability
|
|
Availability
|
Maintainable
|
|
Manageable
|
Scalability
|
|
Usability
|
Performance
|
|
Regulatory
|
Environmental
|
|
Throughput (QPS, read/write)
|
Latency
|
|
R/W ration
|
Traffic Estimates - write(QPS, volume of data) and read (QPS volumen of data
|
|
Storage Estimates
|
Memory Estimates (Cache, what kind of data in it)
|
|
RAM
|
SSD or disk
|
|
Use case
|
Scenarios to not cover
|
|
who will use
|
How many will use
|
|
Usage patterns
|
|
|
Latency / throughput requests
|
|
Consistency vs Availability
|
|
- weak / strong or eventual consistency
|
|
- failover / replication availability
|
|
APIs for read write scenario
|
DB schema
|
|
Basic algo
|
HLD for Read/write scenario
|
No comments yet.
Cheatography n. The art of mapping complex subjects into clear, instantly navigable reference guides.