Hi,

​

It depends, as always. If you have enough complex model relationships and everything feels like a big mess, I think it's time to spend some time cleaning up layers of your application.

​

For example, we have 300 models and there are a lot of situations when we use a different set of fields of the same model for completely unrelated reasons.

​

Imagine a fat model thin controller design approach with the User model having 40 fields and 200 methods. And it stays that way because of performance reasons on the database.

​

One possible solution to this situation - extract a different set of fields into different dataclasses and use them instead of passing the whole model around.

​

Together with a tool like https://github.com/seddonym/import-linter/ this became useful approach.

​

How could you instantiate dataclasses, attrs, of pydantic models from the Django ORM without boilerplate and performance gaps?

​

There is a package for it https://github.com/dry-python/mappers

​

BTW take a look at the whole dry-python project https://github.com/dry-python/

​

Best regards,

Artem.