I am developing a SQL database web application from scratch. The application will manage information for customers working in the same form. In other words, the information (entities and relationships between them) regarding each client does not change too much from one to the other. However, the amount of information is dictated by the size of the company. The application can be hosted on our server (s) or anywhere that the client selects.
My first question is: what are the pros and cons of the following options:
- A. Manage multiple customer information in the same database;
- B. Management of one customer information per database; therefore, each client will have its own database;
My second question is: what are the pros and cons of the following deployment methods?
- A. Each client receives its own server (node);
- B. Use a large RAID drive with one powerful server with multiple websites;
Since the decisions on these choices affect my design, I would like to know the pros and cons from different points of view, including service, cost (financially and on time) and architecture, to name a few.
Technologies used:
- Database: MS SQL
- Platform: ASP.NET
- Language: C #
Any comments or suggestions are welcome,
Thanks,
Cullen