Design a Search Service

Last updated: June 14, 2026

Quick Overview

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

Morgan Stanley
System Design
Software Engineer
Morgan Stanley
June 14, 2026
Software Engineer
System Design Round
System Design
Medium

5

10

3,330 solved


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

This is a common system design question asked during System Design Round at Morgan Stanley. 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. Morgan Stanley 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
Message queues and async processing
API design and rate limiting
Partitioning and sharding strategies
Security and authentication
High-level architecture and component design
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 a region-wide outage?
  • What would the deployment pipeline look like for this system?
  • How would you handle a 10x increase in traffic overnight?
  • How would you handle schema migrations with zero downtime?
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. Search Functionality: Users must be able to perform geo-based searches across various data sources (e.g., financial data, market trends, client portfolios).
  2. **Aut...
Capacity Estimation

Back-of-Envelope Calculations

  • User Base: Assume 100,000 active users.
  • Search Requests: Assume each user performs 10 searches per day.
  • Total Daily Search Requests: 100,000 users *...

Submit Your Answer
Markdown supported

Related Questions