Design a Messaging for Supabase
Last updated: January 15, 2026
Quick Overview
Design a geo-distributed messaging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Supabase
January 15, 20263
12
4,263 solved
Design a geo-distributed messaging system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
This is a common system design question asked during Technical Screen 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
- 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
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- What would the deployment pipeline look like for this system?
- How would you implement rate limiting to protect the system?
- What happens if one of your database nodes goes down?
- How do you ensure data consistency across multiple services?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
Functional Requirements
- Messaging: Users should be able to send, receive, and delete messages in real-time.
- User Presence: Indicate whether users are online or offline.
- **Group Me...
Capacity Estimation
Assuming Supabase aims to support 10 million active users with an average of 100 messages sent per user per day:
- Total Messages: 10,000,000 users * 100 messages = 1 billion messages daily.
- **P...