A Bigtable table uses monotonically increasing timestamps at the beginning of every row key and writes concentrate on one key range. Which approach best fits?

Published
  1. Evaluate an appropriate index using the query plan and write-cost tradeoff.
  2. Use a database transaction covering the required consistency boundary.
  3. Use a cache with explicit invalidation or expiration rules.
  4. Redesign row keys to distribute writes while preserving required access patterns.

Comments — 0