I am doing a system in Laravel, however this system will serve several users, and these users could register their clients.
The big question is, in order not to be all in one database, I thought every time the user registered in the application, create a new database, and within that database to run the migrations of the tables.But each user can register their clients and these clients will have user and password, in the login I would have to go bank to bank to know which bank is that client to do the authentication ... then I did not find a legal practice, another option is to ask for an identifier when logging in, but I do not think it would be good practice either.
The last option is to create a single database with all the data, so the tables would be huge ...
Could any architect give me a light?