All Questions
Sharding easy

In 'Range-Based' sharding (e.g., Shard A stores users with names A-M, Shard B stores names N-Z), what is a significant operational risk?

  1. A It requires an expensive lookup service for every single query.
  2. B It makes it impossible to perform range queries efficiently.
  3. C It often leads to 'Hotspots' if the data distribution is non-uniform (e.g., more users having names starting with 'S' than 'X').
  4. D It cannot be used with integer-based ID columns.

One system design question a day, with spaced repetition so the ones you miss come back.

Get the app

Related questions