InterviewStack.io LogoInterviewStack.io

Database Architecture and Partitioning Questions

Design database architecture and partitioning strategies appropriate to workload and access patterns. Evaluate database types including relational and various NoSQL models, schema design and indexing strategies, and when to use a monolithic database versus sharding. Cover sharding approaches such as range based, hash based, consistent hashing, and directory based sharding, as well as replica topologies, read replicas, replication lag, and handling cross shard queries. Address operational concerns at scale: resharding, mitigating hot partitions, balancing data distribution, transactional and consistency guarantees, and the trade offs between availability, consistency, and partition tolerance. Include monitoring, migration strategies, and impact on application logic and joins.

MediumTechnical
51 practiced
Compare directory-based sharding (a lookup service that maps keys to shards) with client-side hashing. For a system with frequent rebalances, which approach simplifies operations, which adds latency, and how would you make the directory service resilient and low-latency?
HardTechnical
55 practiced
Implement a consistent hashing ring with virtual nodes in Python. Provide functions: add_node(node_id), remove_node(node_id), and get_node_for_key(key). Ensure your implementation supports efficient lookup, describe complexity, and explain how you minimize key movement when nodes are added/removed.
EasyTechnical
52 practiced
Compare relational databases with document stores and wide-column NoSQL models for storing high-volume telemetry (time-series) data. Discuss schema design, indexing strategies, compaction/GC behavior, and operational differences an SRE should expect when selecting one for telemetry ingestion and retention.
MediumTechnical
56 practiced
Explain consistent hashing and how virtual nodes (vnodes) reduce imbalance. As an SRE, describe how you'd implement a consistent hashing ring so adding/removing nodes causes minimal key movement and what metrics you would collect to verify even distribution.
MediumSystem Design
54 practiced
Design a replication topology for a globally distributed read-heavy service operating in 4 regions. Requirements: low read latency per region, acceptable asynchronous replication for cross-region durability, and clearly defined failover behavior. Describe reader routing, replication lag handling, and promotion strategy.

Unlock Full Question Bank

Get access to hundreds of Database Architecture and Partitioning interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.