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.

MediumSystem Design
0 practiced
Design a global multi-region database strategy for low-latency reads across regions while ensuring consistent writes in one master region. Discuss replication model, failover, read-routing, conflict resolution, and how to measure RPO/RTO for the solution.
HardSystem Design
0 practiced
Design a backup and point-in-time recovery (PITR) strategy for a sharded transactional database ensuring consistent recovery across shards. Describe snapshot coordination, WAL/CDC capture, retention policy, and the operational steps to restore to a given timestamp.
EasyTechnical
0 practiced
Describe basic replica topologies used in production: primary-secondary (master-slave), multi-primary (multi-master), and leaderless architectures. For each, explain read/write flow, typical use cases, and a key operational caveat.
EasyTechnical
0 practiced
List and briefly describe common sharding approaches: range-based, hash-based, consistent hashing, and directory-based sharding. For each approach, give one workload example where it fits well and one where it is a poor fit.
HardTechnical
0 practiced
Design a solution for cross-shard ACID transactions in a financial system where transferring funds requires strong consistency across two account shards. Evaluate two-phase commit (2PC) vs an application-level compensation/SAGA approach, and recommend architecture and operational controls.

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.