Design a large-scale Messaging Platform

Last updated: July 23, 2025

Quick Overview

Design a scalable messaging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Supabase
System Design
Product Manager
Supabase
July 23, 2025
Product Manager
Onsite
System Design
Medium

449

9

4,600 solved


Design a scalable messaging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

This is a common system design question asked during Onsite at Supabase. The interviewer expects you to demonstrate your ability to design large-scale distributed systems, make well-reasoned trade-offs, and communicate your thought process clearly. Supabase values engineers who can think about scalability from day one.

What the Interviewer Expects
  • Systematically gather requirements and estimate capacity (QPS, storage, bandwidth)
  • Design a scalable architecture with clear component responsibilities
  • Make well-reasoned database and caching decisions with trade-off analysis
  • Address consistency vs availability trade-offs specific to the use case
  • Discuss partitioning strategy, replication, and data modeling
  • Cover failure handling, monitoring, and alerting strategies
Key Topics to Cover
Failure handling and fault tolerance
Database selection and data modeling
Load balancing and horizontal scaling
High-level architecture and component design
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 migrate from a monolithic to a microservices architecture?
  • How do you ensure data consistency across multiple services?
  • How would you handle a region-wide outage?
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

  • User Registration and Authentication: Users must be able to register, log in, and manage their profiles.
  • Messaging: Real-time sending and receiving of messages, i...
Capacity Estimation

Back-of-Envelope Calculations

  • User Base: Targeting 10 million active users.
  • Messages Per User: Assuming an average user sends 10 messages per day, that's 100 million messages daily.
  • **...

Submit Your Answer
Markdown supported

Related Questions