This website uses cookies to ensure you get the best experience.
Learn more.
A database's primary bottleneck is repeated identical read traffic, and a bounded staleness policy is acceptable. Which approach best fits?
Published
- Use a cache with explicit invalidation or expiration rules.
- Redesign row keys to distribute writes while preserving required access patterns.
- Use a database transaction covering the required consistency boundary.
- Evaluate an appropriate index using the query plan and write-cost tradeoff.
Comments — 0
Sign in to comment