Design a File Storage for Coinbase

Last updated: May 13, 2026

Quick Overview

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

Coinbase
System Design
Software Engineer
Coinbase
May 13, 2026
Software Engineer
System Design Round
System Design
Hard

0

13

513 solved


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

System design interviews at Coinbase typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.

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
Message queues and async processing
High-level architecture and component design
Requirements gathering and capacity estimation
API design and rate limiting
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 schema migrations with zero downtime?
  • 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 Codemia
Sample Answer
Requirements

Functional Requirements

  1. File Upload/Download: Users must be able to upload files (up to 5GB) and download them with minimal latency.
  2. Versioning: Support file versioning to allow user...
Capacity Estimation

Assuming Coinbase has around 100 million active users, and each user uploads an average of 5 files per month:

  • Monthly Uploads: 100 million users * 5 files = 500 million files/month.
  • **Daily U...

Submit Your Answer
Markdown supported

Related Questions