Should the project be split?

Question

Software design

There are 3 user groups on the site - admin, stores, users. The account

for stores will be large and functionality will be constantly added like in the admin panel, is it worth dividing the project into 3 projects - one for working with clients, the second for the store admin panel and 3 admin panel itself? Or use one monolith?

Answer 1

This is your job - to make such decisions based on a detailed understanding of the project and its development plans .
Uncles and aunts from the Internet cannot do it for you, because they do not have a detailed understanding of the project and they do not know development plans. Uncles and aunts from the Internet can only say the abstract pros and cons of separating or not separating an abstract project, but this information does not translate well to real projects.

Answer 2

No. You can add route files separately for each. Folders for controllers for each. You can even put it all in modules. You can easily share it all in one project.
Otherwise, you will have to constantly synchronize models (General ones will be 100%), constants, configs, update 3 and not 1. IMHO, dividing you will only get unnecessary worries.
But everything changes if the admin panel is a SPA and data exchange via APi, then you can separate and not worry.

Answer 3

The answer depends on the architecture of the frontend. But if you separate, then you can separately select common components for all roles.