For too long I’ve been doing “fat views, thin models” in practice. Only very recently did I realize (through learning from the veterans) that business logic is better handled outside of the views. So I refactored a project and moved almost all of the business logic from views to models, following so…

I tend to keep my tasks.py very, very short. I don’t really know why, but I don’t like having much logic in there - I see it as only an entry point for a process to call other code. But that doesn’t mean I’ll put all the logic in models or managers. I often end up creating entirely new modules for …

One thing that I find helps to reduce the mental load of having a huge models.py file, is to break up your models into separate files. Even on smaller projects, I usually start with: my_app - models - __init__.py - model_one.py - model_two.py - etc... I keep the model and its man…

Thanks for sharing your experience. I like your approach. An extra benefit of breaking a huge models.py down is that it’s easier to include a sub-model in the context window of LLMs. As for the approve() and publish() in the article, I agree with you: in this case it makes more sense to implement i…

By the way, do you tend to include the logic in tasks.py in your models?

I agree with Phil’s approach, I would tend to keep the tasks lean and encapsulate the business logic in a separate class or module.

Agree with Phil as well. It’s a pattern that the few medium/big projects I worked on moved to eventually. We called the module/package for business logic operations.py or split it into a folder when it got too big. Another project called this “commands” (although I personally find this a bit confusi…

This is a topic that has been discussed here in the past, you might want to search for some of the other threads discussing issues like this. (I’ve included some links at the bottom to help you get started.) I’m going to share the contrary view to the prior response. Models: “Fat models” for meth…

Really like your approach. I feel doggedly keeping business logic outside of the views can be a pain and may drag down the development progress. You approach is more flexible.

[image] KenWhitesell: What constitutes “too big”? Our empirical evidence has shown that code files tend to become unmanageable at about 2500 lines. So we start looking to refactor when they go above 2000. What we don’t do is unnecessarily proliferate the number of files. We never start from the…

Fat models, thin views, what about tasks

Using Django Getting Started

Adammm01 September 1, 2025, 4:51am 11

Thanks, its really helpful.

Topic		Replies	Views
Where to put business logic in Django? Using Django	13	52620	June 23, 2021
Business logic: what's the effort to switch between approaches? Using Django	15	447	May 20, 2026
Whats the correct way to add logic to a view Using Django	1	3357	December 14, 2021
Combining Django's django.db.models.Model + abc.abstractmethod Getting Started	15	2884	June 3, 2021
Combining Urls, Views, Forms, and Models into fewer files Getting Started	6	8764	August 15, 2023

Fat models, thin views, what about tasks

Related topics