Dashboard/System design/28. Design Quora

SYSTEM DESIGN · LESSON 28 OF 52 · 12 MIN VIDEO · 5 TOPICS

Design Quora

Module Progress (0 / 5 Lessons Completed)0%
System design Track (0 / 52 Modules) · Overall 0/80 (0%)0%
⌁

Narrated HD Video Lesson (12 min) · Pro

Lesson Overview + Section #01 + RESHADED Checklist + Quiz #1 are unlocked free below (no login required). Unlock all 80 HD video lessons and deep-dive sections — or watch our two free sample video lessons first.

SYSTEM DESIGN VIDEO LESSON & GUIDE

Design Quora

Designing Quora tests how an engineer scales a knowledge-sharing Q&A platform serving 1 billion monthly users (300 million DAU) where reads outnumber content writes by more than 300:1 (6 billion daily reads vs. 18 million new questions and answers), every question page requires ML-ranked answer ordering, and answers embed rich media. L4-L6 interviewers look for an iterative progression from a clean relational baseline (MySQL + Memcached + CDN) to vertical functional partitioning, question_id-colocated horizontal sharding, Kafka-decoupled side effects, and MyRocks latency optimization.

WHAT YOU WILL MASTER IN THIS LESSON
  • Quantify Quora's 300:1 read-heavy workload (69K average / 139K peak RPS, 1.2 TB/day storage, 56 Gbps egress) to prioritize read caching, media CDN offload, and asynchronous write pipelines.
  • Design an initial relational core paired with Redis live view counters, HBase/MyRocks analytical history, and off-path ML ranking clusters.
  • Evolve a single MySQL bottleneck through vertical table-group partitioning and horizontal sharding by question_id behind a location-transparent shard router.
  • Decouple follower notifications, home-feed fan-out, and search indexing via Kafka while enforcing read-your-own-writes consistency for authors.
SYSTEMATIC INTERVIEW CHECKLIST · RESHADED + 45-MIN CLOCK

8-Step RESHADED Execution Checklist

Follow this exact sequence from the Intro narration on every system design prompt so you never miss requirements, math, contracts, or the 13-minute deep dive.

0 / 8 Checked
INTERVIEWER SCORECARD · WHAT MAKES A STRONG HIRE?

5 Signals Bar Raisers Grade (L4 vs. L5 Senior vs. L6 Staff)

Senior (L5 / E5 / Senior SDE) Bar — Autonomous Pacing, Depth & Proactive Trade-Offs: Owns the 45-minute clock without prompting, derives every component quantitatively, surfaces failure modes (hot shards, stampedes, dual writes) BEFORE being asked, and defends consistency vs. latency trade-offs.
1. Scoping
✓ STRONG HIRE SIGNAL

Clarifies users, read/write skew, p99 latency, consistency bounds, and explicit non-goals in minutes 2–8.

✗ NO-HIRE RED FLAG

Jumps straight into drawing load balancers and microservices at minute 2 without asking a single question.

2. Right-Sized Design
✓ STRONG HIRE SIGNAL

Starts with the simplest working architecture justified by the math (e.g., 1 NVMe SQL primary + replicas + Redis for 40 writes/s & 3 TB).

✗ NO-HIRE RED FLAG

Recites a memorized Kafka + multi-DC Cassandra diagram that contradicts their own traffic calculations.

3. Technical Depth
✓ STRONG HIRE SIGNAL

Drives deep into 1–2 hard bottlenecks (partition keys, hot-key mitigation, transactional outbox, KV-cache batching) at minute 27.

✗ NO-HIRE RED FLAG

Skims across 12 boxes at identical buzzword depth and runs out of time before the deep dive.

4. Explicit Trade-Offs
✓ STRONG HIRE SIGNAL

Uses 3-part reasoning: 'A queue here because SMTP spikes to 3 s; checkout stays <60 ms, and we accept eventual email delay + retry dedup.'

✗ NO-HIRE RED FLAG

Name-drops tools ('We put Kafka and ZooKeeper here') without stating the alternative or operational cost.

5. Communication
✓ STRONG HIRE SIGNAL

Thinks aloud every 30–45s, checks alignment at phase transitions, and treats 'What if X fails?' as a cue for where points are awarded.

✗ NO-HIRE RED FLAG

Goes silent for 5 minutes while drawing or defends a flawed assumption defensively when nudged.

ARCHITECTURE & DATA-FLOW SLIDES · SLIDE 1 OF 1Section 01: System Design: Quora
ARCHITECTURE / DATA FLOW DIAGRAM
Askerone userfive lessonsQuestionone page812 upAnswer Atext, imageAnswer Btext, videoAnswer Cpersonal feedReadersmillions
SECTION 01 OF 5

1. System Design: Quora

★ FREE PREVIEW
Key Takeaway: Quora combines extreme read-to-write asymmetry (> 300:1), multimodal long-form answers, and continuous ML quality ranking—requiring aggressive pre-computed caching on reads and strict off-path execution for scoring and fan-out.
ARCHITECTURE / DATA FLOW DIAGRAM
Askerone userfive lessonsQuestionone page812 upAnswer Atext, imageAnswer Btext, videoAnswer Cpersonal feedReadersmillions

Defining Workload Traits of a Global Q&A Platform

On Quora, a single canonical question—such as "What is the fastest way to learn system design?"—accumulates dozens of rich answers, hundreds of comments, thousands of upvotes/downvotes, and millions of long-tail reads arriving from web search engines over years. Three structural properties distinguish Quora from chronological chat or microblogging systems: an overwhelming read-to-write ratio, rich media attachments inside long-form text, and algorithmic quality ranking on every single page render.

  • Extreme read dominance: Organic search traffic drives hundreds of passive page reads for every question asked or answer written, making Memcached hit ratios the primary determinant of infrastructure cost and p99 latency.
  • Media-rich answers: While questions (~1 KB) and prose answers (~5 KB) are compact, embedded high-resolution diagrams (~250 KB) and videos (~10 MB) dominate storage bytes and network egress.
  • ML-ranked ordering: Unlike chronological forums where ORDER BY created_at DESC suffices, Quora scores every answer by upvote velocity, author domain credibility, and view engagement, plus curates personalized topic/author feeds.

Quora vs. Chronological Microblogging Feeds

Candidates often conflate Quora with Twitter/X, applying pure push-based social graph fan-out without accounting for search-landed canonical question pages where non-chronological quality ranking is paramount.

DimensionChronological Microblog (Twitter/X)Knowledge Q&A Platform (Quora)
Primary Read SurfaceEphemeral user home timeline (last 24h)Evergreen canonical Question Page + personalized topic/author feed
Sort Order on PageTimestamp or lightweight engagement sortMulti-feature ML quality score (upvotes, author reputation, dwell time)
Payload CompositionShort text (<= 280 chars) + media linksMulti-paragraph formatted prose (~5 KB) + inline images and videos
Co-Location Keyuser_id (author's recent posts)question_id (question + all answers rendered together on one page)
SECTION 02 OF 5

2. Requirements of Quora's Design

🔒 PRO SECTION
Key Takeaway: With 300M DAU generating 139K peak RPS (6B reads/day against 18M content writes/day) and 1.2 TB/day of text and media, Quora requires sub-second availability, author read-your-own-writes consistency, and ~280 stateless service hosts.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

SECTION 03 OF 5

3. Initial Design of Quora

🔒 PRO SECTION
Key Takeaway: A clean v1 architecture separates stateless web/application tiers, stores relational Q&A and votes in MySQL fronted by Memcached, offloads images/video to Blob storage + CDN, buffers 69K/s view increments in Redis -> HBase, and runs ML ranking offline—exposing two remaining bottlenecks at scale.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

SECTION 04 OF 5

4. Final Design of Quora

🔒 PRO SECTION
Key Takeaway: Quora's production-scale design eliminates the single-DB and synchronous-write bottlenecks via two-stage MySQL sharding (vertical table partitioning followed by horizontal sharding on question_id), Kafka-driven asynchronous worker fan-out, consolidated service hosts, and MyRocks storage.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

SECTION 05 OF 5

5. Evaluation of Quora's Design

🔒 PRO SECTION
Key Takeaway: Quora's final architecture achieves linear scalability, high availability, sub-second reads, and author read-your-own-writes consistency, while mitigating viral hot-question shard overload via multi-tier caching and request coalescing.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

ACTIVE RECALL & TRADE-OFF PROBES

System Design Checkpoint Quizzes (1)

CHECKPOINT QUIZ #1

In "System Design: Quora" (Quora vs. Chronological Microblogging Feeds), how does a production-grade design handle "Sort Order on Page" (Knowledge Q&A Platform (Quora))?