Architecture Laravel

1

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?

    
asked by anonymous 10.09.2018 / 07:16

1 answer

0

I have a similar scenario, but in my case, I have a "club" database, where you have your login data and database access data for each one, as soon as you log in, I perform the search within the club database, and then find it, I get the data to access my own database, where it contains the data of specific users of that club.

    
14.09.2018 / 15:03