How Do You Know How Many Controllers To Make In Laravel?

In Laravel, the number of controllers you need to create depends on the complexity and requirements of your application.

However, as a general rule, you should create a separate controller for each distinct functional area of your application.

– This helps to keep your code organized and modular, making it easier to maintain and test.

For example, suppose you have a blog application. In that case, you might have a:

• PostsController for handling post-related actions (such as displaying a list of posts, displaying a single post, creating a new post, etc.),
• CategoriesController for handling category-related actions, 
• and a CommentsController for handling comment-related actions (such as adding a new comment, deleting a comment, etc.).

Ultimately, the number of controllers you need will depend on the specific requirements of your application.

You should balance having:

–  too many controllers (which can make your codebase harder to navigate) 
– and having too few controllers (which can result in controllers that are too complex and difficult to manage).