Moderate SQL Question 96 of 226

When is denormalization the right call in a Flipkart-style catalog?

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

PICTURE THIS: DATABASE INDEX

Without indexScan every row

With indexJump to keys

CostWrites slower

Simple meaning

When a read path must join five tables on every product card and p99 latency is too high.

WHY — SQL instead of guessing?

Why interviewers care about SQL:

They are checking judgment

on SQL.

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.

STEPS — What happens step by step?

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

1
When a read path
must join five tables on every product card and p99 latency is too high.
2
You store a redundant
brand name or rating summary on the product row or in a document cache, and you accept the job of keeping it in sync.
3
Normalization remains the source
of truth for writes.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

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

Say this line

“You store a redundant brand name or rating summary on the product row or in a do”

Break into beats

Youstorearedundantbrandname

Speaking order

2987408337471632900

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

Key takeaway

When a read path must join five tables on every product card and p99 latency is too high. You store a redundant brand name or rating summary on the product row or in a document cache, and you accept the job of keeping it in sync.