When would you use a function-based or class-based Django view?

Chooses Django view style by clarity, reuse, and lifecycle needs rather than hierarchy preference.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I use a function-based view when the request flow is small and explicit. I use a class-based view when HTTP methods share setup or when Django's generic views provide a close match for common list, detail, form, create, or update behavior. Class-based views offer reuse through inheritance and mixins, but their dispatch and method-resolution flow can be harder to follow.

Full answer below

Practice focus

A balanced trade-off between explicit functions and reusable class-based 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.
Overview
Both view styles can be correct; the useful choice is the one that keeps request behavior clear.
I use a function-based view when the request flow is small and explicit. I use a class-based view when HTTP methods share setup or when Django's generic views provide a close match for common list, detail, form, create, or update behavior. Class-based views offer reuse through inheritance and mixins, but their dispatch and method-resolution flow can be harder to follow.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I start from the simplest readable implementation and adopt a generic view only when it removes real repetition. If I override most hooks or stack many mixins to force a unique workflow into generic CRUD, a function or a smaller custom class is usually clearer. Business logic should be callable outside either view style, so changing the adapter does not rewrite the use case.

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

Calling class-based views inherently more advanced.
Using generic views while overriding nearly all their behavior.
Placing business rules in whichever view style was chosen.

When would you use a function-based or class-based Django view?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Tech stacks

Skill areas

Suggest an improvement

Found this answer useful?