The architecture must support the use cases. [...] This is the first concern of the architect, and the first priority of the architecture.
If Laravel's native architecture can support your use cases, which is likely to be the case for small / mid size or early project, then yes, maybe you don't need Clean Architecture.
As the system's architect (apointed or de-facto) it is your responsibiliy to pick the best architecture you can given the project, its scope, its constraints, and its team.
If CA is overkill, then pick something simpler 👍 Just make sure you can migrate later as the project grows.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for your comment Bernard.
As I quote in the article
If Laravel's native architecture can support your use cases, which is likely to be the case for small / mid size or early project, then yes, maybe you don't need Clean Architecture.
As the system's architect (apointed or de-facto) it is your responsibiliy to pick the best architecture you can given the project, its scope, its constraints, and its team.
If CA is overkill, then pick something simpler 👍 Just make sure you can migrate later as the project grows.