Discussion on "Django Service Layers: Beyond Fat Models vs. Enterprise Patterns"

Simon Crowe · 2024-06-16T13:11:30.160Z

Suppose you want to write a new Django/DRF API service tomorrow or have inherited a large but messy Django codebase. Introduction If your application is useful, it will do more than enable crud operations on relational database tables via HTTP. Let's...

That's a good question. I haven't worked with forms in years but I can say a couple of things about serializers.

In HackSoft's styleguide they recommend using serializers for data validation/presentation only. In their examples, the serializers are nested in the view class and don't interact with the service layer. (github.com/HackSoftware/Django-Styleguide)

At my company, we ended up calling the service functions from inside the serialisers' create and update methods (django-rest-framework.org/api-guide/serializers). This allowed us to make better use of the GenericAPIView classes (django-rest-framework.org/api-guide/generic-views).

Discussion

Django Service Layers: Beyond Fat Models vs. Enterprise Patterns

Responses(1)

Recent discussions

Search Hashnode

Django Service Layers: Beyond Fat Models vs. Enterprise Patterns

Responses(1)

Recent discussions