I am in the process of designing my CMS which I am about to make, I was thinking about the database and How to reach it.
Do you think the best option is to create 1 master database for all your customers' websites? Or should there be 1 database per site?
What is the profit and the negative on both methods? I am always thinking about the future so that I was thinking of implementing a Memcatch or APC cash in the project, to provide an option for my customer.
Just trying to know the best practices
I run both My business chooses to separate client-specific data into different tables, so that if someone gets corrupted, then not everyone is taken down. This can never happen in an ideal world, but Murphy's law. It seems very easy to find different things with them. You know with 100% certainty. Will that will never appear on a customer's content to another page.
If you go down that route, be prepared to create a script that will prepare and configure the database for you. There is no fun in creating a great system and demanding for it, only to set up your time manually and install the whole day is fun to install. Also, setting up a DB name is an additional step which is not a part of using the single DB table - it is a headache that will repeat itself and repeat it again.
Comments
Post a Comment