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
52 practiced
Explain how caching layers (application cache, Redis, CDN) and data locality strategies interact with sharded databases. As SRE, propose cache placement and invalidation strategies to reduce cross-shard traffic and prevent cache-driven hotspots during resharding or failover.
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.
EasyTechnical
63 practiced
Given a high-cardinality telemetry stream (events per user arriving at high write rates) explain how you would choose a partition key to balance write throughput and query patterns for retention/TTL and bulk deletes. Compare user_id-only, time-only, and hybrid composite partition keys and explain SRE operational implications.
HardSystem Design
65 practiced
A banking system requires strong consistency for inter-account transfers across shards at 50k TPS. Compare using 2PC with a distributed transaction coordinator versus sharding to co-locate related accounts (so most transfers are local). Discuss trade-offs in latency, throughput, complexity, availability, and operational burden, and recommend an approach that meets ACID and SLO constraints.
MediumSystem Design
46 practiced
Design an automated failover system for primary-replica database pairs that minimizes split-brain risk. Describe health checks, fencing mechanisms (e.g., using an external consensus system), promotion safety checks, and how SREs should validate and audit automatic promotions.

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.