Business logic in django

So where do we put business logic in Django?

Here are 4 possible solutions:-

Idea #1: Fat Models
I believe that the “default” idea supported by Django documentation is to make your models “fat.” 
To put it colloquially, this approach suggests that if you don’t know where some of the code should go, 
and it somehow relates to the object (and what doesn’t?), then it’s best to put it in the model.

Idea #2: Putting Business Logic in Views/Forms
Another idea is to place business logic in forms or views.
Though I’ve seen it being seriously suggested, 
I don’t think that putting business logic in forms, views, or serializers is a clean idea.

Idea #3: Services
Another commonly advocated idea is that it’s worth to add a separate layer of code called services between views and models. 
That is quite unusual in a vanilla Django system but some projects successfully employ that method.

To read full article click on the Source link below.

Source: sunscrapers.com

Similar codes

2 votes261 views2 answers
Django exclude queryset
Python Django
0 vote243 views2 answers
Style django forms with crisp
Python Django
17 votes324 views6 answers
Installing django
Python Django
1 vote279 views1 answer
Django get part of queryset
Python Django
0 vote254 views2 answers
How to avoid inserting duplicate records in orm django
Python Django
28 votes330 views3 answers
Django abstractuser
Python Django
3 votes263 views2 answers
Django postgres connection
Python Django
0 vote247 views1 answer
Add header info in django response
Python Django
0 vote258 views1 answer
Django admin readonly models
Python Django
0 vote304 views1 answer
Django create username and password from csv
Python Django