Architect a geo-distributed Recommendation Engine

Last updated: February 23, 2026

Quick Overview

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

Salesforce
System Design
Software Engineer
Salesforce
February 23, 2026
Software Engineer
Technical Screen
System Design
Medium

1

6

4,311 solved


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

Salesforce asks this during the Technical Screen to assess your architectural thinking. They want to see how you decompose a complex problem, choose appropriate technologies, and reason about failure modes. Strong candidates proactively discuss monitoring, alerting, and operational concerns.

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
API design and rate limiting
Security and authentication
Requirements gathering and capacity estimation
Caching strategies (local, distributed, CDN)
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 migrate from a monolithic to a microservices architecture?
  • How would you handle a region-wide outage?
  • What happens if one of your database nodes goes down?
  • How would you handle a 10x increase in traffic overnight?
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. User Interaction: The recommendation engine will provide personalized product recommendations for users based on their historical interactions and preferences.
  2. **...
Capacity Estimation

To estimate capacity, let's assume:

  • Daily Requests: 10 million recommendations.
  • Peak Load: 20% of the total requests occur during peak hours.
  • QPS Calculation: (10 million / 24 hours)...

Submit Your Answer
Markdown supported

Related Questions