Is that a good idea to use one database for 50.000+ shops?
We are developing an internet application in C# with MVC 4. It's connected to a database which will contain a companies customers and their turnovers, also the products.
Naturally,these companies want their data secured, and also the data needs to be brought from the database to the web application as quickly as possible.
We are unsure what is the most secure and performance effective approach:
Have one smaller database for each company, containing their customer data. This way the only "weak" human link is to code the connection string correct depending on who's logging in.
Use one single database containing every companies data and all their customer data. This will naturally be a very much larger database, and possible(?) more room for error, leading to one employee seeing another companies turnovers. A critical situation.
What solution might be most secure, and the fastest in crunching numbers and processing it to the web application? is this a common "security" solution, to minimize human error by giving each company their own database?