Design Marketplace

Last updated: January 9, 2026

Quick Overview

Design the architecture for Marketplace. Cover scalability, data storage, caching, and real-time requirements.

Meta
System Design
Software Engineer
Meta
January 9, 2026
Software Engineer
System Design Round
System Design
Medium

116

7

1,830 solved


Design the architecture for Marketplace. Cover scalability, data storage, caching, and real-time requirements.

This is a common system design question asked during System Design Round at Meta. 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. Meta 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
Monitoring, logging, and alerting
Message queues and async processing
Load balancing and horizontal scaling
Requirements gathering and capacity estimation
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?
  • What monitoring and alerting would you set up on day one?
  • How would you implement rate limiting to protect the system?
  • How would you optimize costs as the system scales?
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 Marketplace, key functional requirements include: what are the core u...

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