How do you choose between APIView, generic views, mixins, and ViewSets?

Chooses the smallest DRF view abstraction that expresses an endpoint clearly.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

APIView gives direct control over HTTP methods while still providing DRF requests, responses, policy checks, and exception handling. Generic views combine GenericAPIView with common actions, and mixins let a class select reusable CRUD behavior. ViewSets group related resource actions and work well with routers. I choose the smallest abstraction that matches the endpoint without hiding important behavior.

Full answer below

Practice focus

Trade-off judgment around control, CRUD reuse, routers, overrides, and discoverability.

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
DRF's view abstractions are a menu of reuse options, not a maturity ladder.
APIView gives direct control over HTTP methods while still providing DRF requests, responses, policy checks, and exception handling. Generic views combine GenericAPIView with common actions, and mixins let a class select reusable CRUD behavior. ViewSets group related resource actions and work well with routers. I choose the smallest abstraction that matches the endpoint without hiding important behavior.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Conventional CRUD with predictable querysets and serializers is a good fit for generics or a ModelViewSet. An operation-oriented endpoint or unusual workflow may be clearer as an or a focused generic view. If I override most hooks, branch heavily on , or fight router-generated routes, the abstraction is no longer saving complexity. Business behavior remains outside the view either way.

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

Using ModelViewSet for every model by default.
Calling lower-level views less maintainable by definition.
Adding many custom actions to avoid defining real resources.

How do you choose between APIView, generic views, mixins, and ViewSets?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section

Tech stacks

Skill areas

Suggest an improvement

Found this answer useful?