Design an in-memory database

Q: Design an in-memory database

This question evaluates understanding of in-memory database engine design, including data model and API surface, in-memory storage layout and indexing, query execution, transaction isolation and concurrency control, durability mechanisms (WAL, snapshots, recovery), and strategies for replication and sharding.

Q: How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

Question

System Design: In-Memory Database Engine (Single-Node Core, Scale-Out Aware)

Context

Design the core of an in-memory, single-node database engine intended to be the building block for a larger distributed system. Data is primarily memory-resident on each node; durability and scale-out are achieved via logging, snapshots, and replication/sharding across multiple such nodes.

Requirements

CRUD operations on records.
Efficient querying: point lookups and range scans; basic filtering and ordering.
Transaction isolation: define levels supported (at least read committed and snapshot isolation; discuss path to serializable).
Persistence and backup: crash recovery, snapshots/checkpoints, WAL, and restore.
Horizontal scalability: strategy for replication and sharding across multiple single-node instances.

Deliverable

Provide a design that covers:

Data model and API surface.
In-memory storage layout and indexing.
Query execution approach.
Concurrency control and transaction management.
Durability: WAL, checkpoints/snapshots, recovery.
Backup/restore strategy.
Horizontal scaling: replication and sharding.
Operational concerns: garbage collection, observability, and pitfalls.

Design an in-memory database

System Design: In-Memory Database Engine (Single-Node Core, Scale-Out Aware)

Context

Requirements

Deliverable

Solution

Comments (0)