Design a geo-distributed Chat System

Last updated: May 20, 2026

Quick Overview

Design a geo-distributed chat system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

DoorDash
System Design
Software Engineer
DoorDash
May 20, 2026
Software Engineer
System Design Round
System Design
Hard

64

5

783 solved


Design a geo-distributed chat system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

System design interviews at DoorDash typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.

What the Interviewer Expects
  • Drive the design discussion proactively with minimal interviewer guidance
  • Perform detailed capacity estimation and use it to inform design decisions
  • Design for global scale with multi-region deployment and data consistency
  • Deep dive into 2-3 critical components with implementation-level detail
  • Address complex trade-offs: CAP theorem, eventual consistency, conflict resolution
  • Discuss operational excellence: deployment strategy, chaos engineering, SLOs/SLIs
  • Propose a phased rollout plan from MVP to full-scale system
Key Topics to Cover
Load balancing and horizontal scaling
Requirements gathering and capacity estimation
Caching strategies (local, distributed, CDN)
Monitoring, logging, and alerting
Database selection and data modeling
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How would you optimize costs as the system scales?
  • How would you handle schema migrations with zero downtime?
  • How would you implement rate limiting to protect the system?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements
  • Functional Requirements:
    1. Real-time messaging: Users should be able to send and receive messages instantly.
    2. Group chats: Support for one-on-one and group conversations.
    3. Messa...
Capacity Estimation
  • User Base Estimation:
    Assuming DoorDash has 30 million active users. If 20% are active in the chat system, that’s 6 million users.

  • Message Estimation:
    If each user sends an av...


Submit Your Answer
Markdown supported

Related Questions