PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/Airbnb

Design a Distributed Key-Value Store

Last updated: Apr 27, 2026

Quick Overview

This question evaluates expertise in distributed systems and large-scale storage design, covering API design, partitioning, replication, request routing, fault tolerance, consistency models, and operational behavior during failures; it is categorized under System Design and database/distributed-systems domains and tests both conceptual understanding and practical application. It is commonly asked to assess architectural thinking about scalability and reliability, including trade-offs between consistency and availability as framed by the CAP theorem, and the ability to reason about system behavior during node failures and network partitions.

  • medium
  • Airbnb
  • System Design
  • Software Engineer

Design a Distributed Key-Value Store

Company: Airbnb

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design a large-scale distributed key-value store similar to a simple NoSQL database. The system should support at least the following operations: - `put(key, value)` - `get(key)` - `delete(key)` Discuss how you would design the API, storage model, partitioning strategy, replication, request routing, fault tolerance, and scaling approach. Explain the consistency model you would choose and the trade-offs using the CAP theorem. Also describe how the system behaves during node failures or network partitions.

Quick Answer: This question evaluates expertise in distributed systems and large-scale storage design, covering API design, partitioning, replication, request routing, fault tolerance, consistency models, and operational behavior during failures; it is categorized under System Design and database/distributed-systems domains and tests both conceptual understanding and practical application. It is commonly asked to assess architectural thinking about scalability and reliability, including trade-offs between consistency and availability as framed by the CAP theorem, and the ability to reason about system behavior during node failures and network partitions.

Related Interview Questions

  • Design a Scalable Job Scheduler - Airbnb
  • Design a Rental Marketplace Backend - Airbnb (hard)
  • Design a booking system - Airbnb (medium)
  • Design a group chat system - Airbnb (medium)
  • Design a real-time chat system with hot groups - Airbnb (hard)
Airbnb logo
Airbnb
Jan 9, 2026, 12:00 AM
Software Engineer
Onsite
System Design
7
0
Loading...

Design a large-scale distributed key-value store similar to a simple NoSQL database.

The system should support at least the following operations:

  • put(key, value)
  • get(key)
  • delete(key)

Discuss how you would design the API, storage model, partitioning strategy, replication, request routing, fault tolerance, and scaling approach. Explain the consistency model you would choose and the trade-offs using the CAP theorem. Also describe how the system behaves during node failures or network partitions.

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Airbnb•More Software Engineer•Airbnb Software Engineer•Airbnb System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,000+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.