Design Reddit - Tradeoffs and Alternatives

Core Decisions

Pros: Accurate counts, better UX Cons: High database load, scaling challenges

Pros: Better scalability, reduced load Cons: Slight delay in counts (5-10s)

Decision: Eventual consistency with 5-second batch updates

Pros: Natural hierarchy, easier queries Cons: Complex updates, depth limits

Pros: Simpler updates, no depth limit Cons: Complex queries, path maintenance

Decision: Nested with parent_comment_id

Pros: Fast reads, consistent results Cons: Storage overhead, update lag

Pros: Always fresh, no storage Cons: Slow reads, high CPU

Decision: Pre-computed with 5-minute cache

Pros: ACID, complex queries, mature Cons: Vertical scaling limits

Pros: Horizontal scaling, high writes Cons: Limited queries, eventual consistency

Decision: PostgreSQL with sharding

Pros: Scalable + accurate Cons: Complex implementation

Decision: AutoModerator + human moderators

Pros: Independent scaling, fault isolation Cons: Operational complexity

Decision: Microservices for scalability

Pros: Better performance, lower database load Cons: Higher cache cost, stale data

Decision: Aggressive caching (90%+ hit rate)

This analysis provides the foundation for Reddit's architecture decisions.