Concept questionHard~9 min

Interview question

Redis latency spikes only for one very popular value. How would you investigate and mitigate it?

Diagnose a hot key causing uneven Redis load

Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would check whether one key pattern receives a disproportionate amount of traffic or stores a very large value. A hot key can overload a Redis node, network bandwidth, serialization, or the app code that processes the cached value. I would look at Redis command latency, key size, endpoint correlation, app instance metrics, and whether spikes line up with a campaign, dashboard, or public page.

Full answer below

Practice focus

Hot keys, traffic concentration, payload size, partition pressure, local caching, sharding, and endpoint behavior.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Hot keys are easy to miss because the overall cache hit rate can look good while one key or endpoint hurts latency.
I would check whether one key pattern receives a disproportionate amount of traffic or stores a very large value. A hot key can overload a Redis node, network bandwidth, serialization, or the app code that processes the cached value. I would look at Redis command latency, key size, endpoint correlation, app instance metrics, and whether spikes line up with a campaign, dashboard, or public page.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Mitigations depend on the data. If the value is small and safe to keep briefly, I might add a tiny local in-memory cache per instance to reduce Redis calls. If the value is huge, I would split it, compress carefully, or change the API shape. If many users need slightly different filtered views, the key design may be too broad or too narrow. For extreme cases, sharding or replicas can help, but I would not start there.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would watch key cardinality, top key patterns where available, Redis CPU, memory, bandwidth, command latency, payload size, and app serialization time. I would compare cache-hit latency with response serialization time because the cache can be fast while the API still spends too much CPU shaping the result. I would also guard against a mitigation that creates stale or inconsistent data across instances. A hot-key fix should reduce concentration while keeping invalidation and freshness still understandable.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Only checking overall cache hit rate.
Increasing Redis capacity without finding the hot key.
Adding local cache with no freshness boundary.
Ignoring large payload serialization cost.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain how one key can hurt the whole cache.
No endpoint/key correlation.
No mitigation besides scale up.
No measurement of value size or bandwidth.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When would a small local cache help?
How can a huge cached value cause latency?
What metrics reveal hot-key behavior?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Try a variant

Answer a similar question in a different context.

CPU or Memory Spike

Opening drill

Concept questionHard~9 min

Interview question

Redis latency spikes only for one very popular value. How would you investigate and mitigate it?

Diagnose a hot key causing uneven Redis load

Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Hot keys, traffic concentration, payload size, partition pressure, local caching, sharding, and endpoint behavior.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Hot keys are easy to miss because the overall cache hit rate can look good while one key or endpoint hurts latency.
I would check whether one key pattern receives a disproportionate amount of traffic or stores a very large value. A hot key can overload a Redis node, network bandwidth, serialization, or the app code that processes the cached value. I would look at Redis command latency, key size, endpoint correlation, app instance metrics, and whether spikes line up with a campaign, dashboard, or public page.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Mitigations depend on the data. If the value is small and safe to keep briefly, I might add a tiny local in-memory cache per instance to reduce Redis calls. If the value is huge, I would split it, compress carefully, or change the API shape. If many users need slightly different filtered views, the key design may be too broad or too narrow. For extreme cases, sharding or replicas can help, but I would not start there.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would watch key cardinality, top key patterns where available, Redis CPU, memory, bandwidth, command latency, payload size, and app serialization time. I would compare cache-hit latency with response serialization time because the cache can be fast while the API still spends too much CPU shaping the result. I would also guard against a mitigation that creates stale or inconsistent data across instances. A hot-key fix should reduce concentration while keeping invalidation and freshness still understandable.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Only checking overall cache hit rate.
Increasing Redis capacity without finding the hot key.
Adding local cache with no freshness boundary.
Ignoring large payload serialization cost.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain how one key can hurt the whole cache.
No endpoint/key correlation.
No mitigation besides scale up.
No measurement of value size or bandwidth.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When would a small local cache help?
How can a huge cached value cause latency?
What metrics reveal hot-key behavior?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Try a variant

Answer a similar question in a different context.

CPU or Memory Spike

Redis latency spikes only for one very popular value. How would you investigate and mitigate it?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Try a variant

Redis latency spikes only for one very popular value. How would you investigate and mitigate it?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Try a variant