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

0 vote189 views1 answer
Django choicefield empty label
Python Django
0 vote166 views1 answer
Django phone number
Python Django
0 vote159 views2 answers
Django rest framework foreign key relation giving error in serializer
Python Django
0 vote259 views3 answers
Django prevent duplicate entries
Python Django
-1 vote164 views1 answer
Raw query in django
Python Django
-4 votes229 views4 answers
Latest version of django
Python Django
0 vote222 views1 answer
Django never_cache example
Python Django
0 vote184 views1 answer
Get token from request django
Python Django
5 votes164 views4 answers
Django get or 404
Python Django
0 vote171 views2 answers
Django-filter
Python Django