What is the essence of the Django project philosophy?

Question

Django

According to the docs, it says that each project can have a bunch of applications and each application can have a project. What is the purpose of such a decomposition? I understand that this is easily migrated to the root project.
How to know: how many applications do you need in a project?

Answer 1

The key is dealing with complexity.
Firstly, different applications can actually contain essentially different services that are rather indirectly related to each other, there is no point in turning them into a single divine application, each application can do something of its own and this is wonderful, in addition to this, there may be, on the contrary, an application that provides some interfaces common to all, so as not to duplicate them.
In addition, if you actually have one service corresponding to one Jungi instance, division into pplications again makes sense, again, to combat complexity, so to speak, encapsulation of oops on a macro scale, divide the project into logical components and each is written in its own application, this is very conveniently.