Moderate Redis Question 117 of 226

When do you store a user object as a Redis hash instead of a JSON string?

Java Specialist · Speak this in 60–90 seconds · Faridabad & Delhi NCR

Without indexScan every row

With indexJump to keys

CostWrites slower

A string GET/SET is simple for a blob you always read whole.

Why interviewers care about Redis:

They are checking judgment

on Redis.

A good answer names

the situation, the default choice, and one exception - that reads as experience.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

Before you speak the answer, walk the interviewer through these steps:

1
A string GET/SET is
simple for a blob you always read whole.
2
A hash lets you
HGET a few fields without deserializing a large JSON.
3
If you always read
the whole profile, a string is fine
4
if you patch one
field often, a hash or a proper database column is cleaner.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

Here's a short line you can speak, broken into clear beats:

Say this line

“A hash lets you HGET a few fields without deserializing a large JSON.”

Break into beats

AhashletsyouHGETa

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

A string GET/SET is simple for a blob you always read whole. A hash lets you HGET a few fields without deserializing a large JSON.