Moderate Vector DB Question 98 of 223

When would you choose HNSW versus IVF-style indexes?

GenAI / LLM · 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

HNSW is a graph index with strong recall and simple incremental inserts, at higher memory cost.

WHY — Vector DB instead of guessing?

Why interviewers care about Vector DB:

They want a clean

contrast on Vector DB, not two memorised paragraphs.

Say what changes for

the developer, then one case where picking wrong hurts.

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
HNSW is a graph
index with strong recall and simple incremental inserts, at higher memory cost.
2
IVF partitions space into
lists and is often cheaper at huge scale with a training step.
3
Choose based on recall,
RAM, and how often you rebuild.
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

“IVF partitions space into lists and is often cheaper at huge scale with a traini”

Break into beats

IVFpartitionsspaceintolistsand

Speaking order

2987408337471632900

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

Key takeaway

HNSW is a graph index with strong recall and simple incremental inserts, at higher memory cost. IVF partitions space into lists and is often cheaper at huge scale with a training step.