Design a large-scale Chat Platform

Last updated: December 6, 2025

Quick Overview

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

Datadog
System Design
Software Engineer
Datadog
December 6, 2025
Software Engineer
System Design Round
System Design
Hard

375

12

4,785 solved


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

System design interviews at Datadog 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
Partitioning and sharding strategies
Security and authentication
API design and rate limiting
Requirements gathering and capacity estimation
Monitoring, logging, and alerting
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 handle schema migrations with zero downtime?
  • How would you migrate from a monolithic to a microservices architecture?
  • What happens if one of your database nodes goes down?
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 Clarification

Before diving into the architecture, clarify the scope with the interviewer. For large-scale Chat Platform, key functional requirements include: what ...

Capacity Estimation

Estimate the scale to drive design decisions. Assume 100M DAU with an average of 10 actions per user per day = 1B requests/day ~ 12K QPS average, ~36K...


Submit Your Answer
Markdown supported

Related Questions