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 vote284 views1 answer
Django default template location
Python Django
0 vote234 views1 answer
Django jwt custom authentication
Python Django
6 votes269 views2 answers
How to check if django is installed( in python shell)
Python Django
2 votes302 views1 answer
Pass in queryset as filter django
Python Django
12 votes307 views5 answers
Django-cors-headers
Python Django
0 vote283 views1 answer
How to run django tests
Python Django
0 vote285 views1 answer
Django rest_framework-social-oauth2
Python Django
0 vote383 views1 answer
Exception Type: AssertionError Exception Value: Expected a `Response`, `HttpResponse` or `HttpStreamingResponse` to be returned from the view, but received a `<class 'django.db.models.query.QuerySet'>`
Python Django
1 vote261 views1 answer
Django form list option
Python Django
0 vote264 views1 answer
Django update request.post
Python Django