Issue NN · Design
[Topic] [Noun]
[One-sentence dek — the single most important constraint or trade-off this design revolves around.]
Read / write ratio
—
Peak QPS
—
Latency target
—
Storage
—
i. Requirements
Functional
- requirement 1
- requirement 2
- requirement 3
Non-Functional
- Availability: …
- Latency: …
- Consistency: …
- Durability: …
- Read/Write ratio: ~X:1
Out of Scope
- item 1
- item 2
ii. Capacity Estimates
| Parameter | Value |
|---|---|
| Daily active users | … |
| Requests per day | … |
| Write QPS | … |
| Read QPS | … |
| Data per record | … |
| Storage (5 years) | … |
| Bandwidth | … |
iii. High-Level Design
[Draw ASCII diagram here]
Client → Load Balancer → Service → Cache → DBWrite path
- step 1
- step 2
- step 3
Read path
- step 1
- step 2
- step 3
iv. Key Design Decisions
[Decision 1]
Options considered: Option A (pros / cons) vs Option B (pros / cons)
[Decision 2]
Options considered: Option A (pros / cons) vs Option B (pros / cons)
Database Choice
See patterns/database-selection.
- Schema: …
- Access pattern: …
- Decision: …
- Sharding key (if applicable): …
Caching
See patterns/caching.
- Strategy: …
- TTL: …
- Eviction: …
- Stampede mitigation: …
v. Deep Dives
[Topic 1 — e.g., Handling hot spots]
Fill in during session…
[Topic 2 — e.g., Consistency trade-offs]
Fill in during session…
[Topic 3 — e.g., Failure scenarios]
Fill in during session…
vi. Failure Modes & Mitigations
| Failure | Impact | Mitigation |
|---|---|---|
| … | … | … |
| … | … | … |
| … | … | … |
vii. Key Takeaways
- takeaway 1
- takeaway 2
- takeaway 3
viii. Patterns to Update
After this session, add/update:
- patterns/caching — [what to add]
- patterns/database-selection — [what to add]
- patterns/[new-pattern] — [if a new cross-cutting pattern emerged]
ix. Go Deeper
- question 1?
- question 2?
- question 3?
❦