A database's primary bottleneck is repeated identical read traffic, and a bounded staleness policy is acceptable. Which approach best fits?

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

Comments — 0