Please enable JavaScript.
Coggle requires JavaScript to display documents.
System design uxdesign.cc - Coggle Diagram
System design
uxdesign.cc
Requirement clarification
Capacity estimation
How many users use the system?
Read-heavy OR write-heavy?
SQL or NO-SQL
The need for caching
Design objectives
Latency & throughput
CAP
Availability & Consistency
API design & algorithms
REST/GraphQL/GRPC
API gateway, Load Balancers
CDN if needed
Algorithm to optimizing the application business
Database, Cache design, Sharding
SQL or NoSQL
Structured or unstructured data
Read-heavy mostly
Speedup by indexing on a column or a set of columns
Design master/slave architecture
write in master & read in slave
-> this isolation speeds up thing
Caching to minimize the IO read
Cache eviction strategies
Caching patterns?
Write through?
Write back?
Cache aside?
Multiple database servers
data partitioning strategies