This website uses cookies to ensure you get the best experience.
Learn more.
A web application reads the same expensive query result thousands of times per minute. Slightly stale results are acceptable for 30 seconds. Which optimization best reduces database load?
Published
- Use a cache-aside strategy with bounded TTLs and an explicit invalidation approach.
- Cache results permanently with no invalidation or expiration.
- Run the expensive query separately for every client and disable all caching.
- Use sticky sessions as a guarantee of database query deduplication.
Comments — 0
Sign in to comment