Is it necessary to use the Repository layer in Laravel?

Is it necessary to use the Repository layer in Laravel? Some people say that many open-source projects are used. Some people say that they do not need to. Therefore, the Repository folder has been deleted from laravel5 and can be completed in the controller. Github also has a package named l5-repository. Let's talk about it. Is it necessary to use the Repository layer in Laravel?
Some people say that many open source projects are used,
Some people say no, so the Repository folder has been deleted from laravel5 and can be completed in the controller.
Github also has a package named l5-repository.
Let's talk about it.

Reply content:

Is it necessary to use the Repository layer in Laravel?
Some people say that many open source projects are used,
Some people say no, so the Repository folder has been deleted from laravel5 and can be completed in the controller.
Github also has a package named l5-repository.
Let's talk about it.

Depending on the project, small projects or projects with independent modules do not need the Repository layer, which is required for projects with complicated and intertwined modules.

I think it is a bit like ThinkPHP's Logic layer. Imagine that when multiple class methods in the control layer need to call the same business Logic, where will you put this business logic, then the Repository will take effect.