Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Multi-Site CMS - Database for every site, or ONE database for all sites?

I'm going to write a multi site content management system in ASP.NET. What will be faster: a database for every site, or one database for all sites?

Thanks.

EDIT: If a database for every site, which database should I use? XML?

like image 421
user145586 Avatar asked Sep 05 '09 18:09

user145586


2 Answers

A single database for all sites may end up being a bad choise in case you have websites with a large number of visits. Also, that means your database tables will have to be more complex, making the system go slower.

About the format of the databases, XML ain't one of them for sure. Try use MySQL or Postgree for instance.

like image 96
yoda Avatar answered Sep 30 '22 16:09

yoda


That really depends on how complicate your CMS will be, if it is a simple micro CMS just like a blog, and you don't have many subscribers for this service, and those subscribers probably have same functions and features on their CMS, then one database could be a choice.

But if your CMS has many granular configuration levels, many functions and features, potentially have large dataset to store. I will recommend separated database for each instance.

File-database, especially Access this kind of database is not designed for online applications, they may have simultaneous connection restrains, so when there are many requests received, it may refuse to serve your web application.

if you are using microsoft technologies, there is no much choice you have for the database, MSSQL probably is the only choice, you may choose SQL Express, but it is not ideal for large sites.

Actually, there are many open source CMS available, even you want to choose microsoft technology based cms, you may try those first to get some feeling on your design.

good luck.

like image 30
machinegone Avatar answered Sep 30 '22 17:09

machinegone