When do you use per-view caching versus template fragment caching?
PICTURE THIS: RAG CHATBOT
Simple meaning
Per-view cache (@cache_page) stores the whole response, which is best for anonymous pages that are identical for everyone.
WHY — Caching instead of guessing?
Why interviewers care about Caching:
contrast on Caching, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
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:
- 1Per-view cache (@cache_page) stores
the whole response, which is best for anonymous pages that are identical for everyone.
- 2Fragment cache ({% cache
%}) stores a piece of a template so the rest can stay personalized.
- 3Vary on cookies or
skip caching entirely for per-user HTML.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Per-view cache (@cache_page) stores the whole response, which is best for anonymous pages that are identical for everyone. Fragment cache ({% cache %}) stores a piece of a template so the rest can stay personalized.