How to distinguish architectural patterns by their purposes and implementation principles?

Architectural patterns differ in purpose and implementation principles as follows:

• MVC (Model-View-Controller): divides the application into three components — model (data), view (UI), and controller (interaction logic). The controller handles user input and updates the model and view.

• MVP (Model-View-Presenter): similar to MVC, but the controller is replaced by a presenter, which contains all the interaction logic between the model and the view. The view is passive and interacts only with the presenter.

• MVVM (Model-View-ViewModel): adds a ViewModel, which connects the model and view through two-way data binding. The ViewModel contains UI logic and state.

• Clean Architecture: separates the system into layers (e.g., presentation, domain, data), each with its responsibilities and depending only on the inner layers. The main principle is dependency inversion.

Each pattern is chosen depending on the requirements for responsibility separation, testability, and application complexity.