Layered architecture in Django: the Service & Selector pattern

Escaping fat models and fat views: where does business logic belong?

The problem

As Django projects grow, views get fat: ORM queries, validation and emails all live in one function.

The fix

Layers: the View accepts the request, a Service handles writes, a Selector handles reads and a Repository owns the ORM.

Comments 0

Be the first to comment!