This website uses cookies to ensure you get the best experience.
Learn more.
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
- Evaluate an appropriate index using the query plan and write-cost tradeoff.
- Use a database transaction covering the required consistency boundary.
- Use a cache with explicit invalidation or expiration rules.
- Redesign row keys to distribute writes while preserving required access patterns.
Comments — 0
Sign in to comment