Architect a low-latency File Storage Engine

Last updated: May 17, 2026

Quick Overview

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

Atlassian
System Design
Software Engineer
Atlassian
May 17, 2026
Software Engineer
System Design Round
System Design
Easy

2

9

694 solved


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

Atlassian asks this during the System Design Round to assess your understanding of the full ML lifecycle. They want to see how you translate a business problem into an ML objective, design the feature pipeline, and plan for model monitoring and retraining.

What the Interviewer Expects
  • Map the business problem to a concrete ML objective
  • Propose reasonable features and a baseline model
  • Discuss basic model evaluation metrics
  • Outline a simple serving architecture
Key Topics to Cover
Model selection and architecture
Model serving and latency optimization
A/B testing and experimentation
Feedback loops and model retraining
Online vs offline evaluation
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
  • What is your model retraining strategy?
  • How would you handle a 10x increase in prediction requests?
  • How would you run A/B tests on different model versions?
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: Support for uploading and downloading files with minimal latency.
  2. Metadata Management: Ability to store and retrieve file metadata such ...
Capacity Estimation

Assuming Atlassian has approximately 10 million users and each user uploads an average of 5 files per week, we can estimate:

  • File Uploads: 10 million users * 5 files/week = 50 million uploads/we...

Submit Your Answer
Markdown supported

Related Questions