s0c0 Posted February 3, 2008 Share Posted February 3, 2008 I am writing a custom CMS for a client. I am trying to decide whether when the CMS creates a new page I should just ad a record in the database containing the information or whether the CMS should create an entirely new file. Here are my concerns: DB Method: It's easier, but the "page" would be accessed using URL GET strings for instance they are on the about.php page and want to access the sucess stories so they click on a link which is really about.php?get=success+stories. What will the load on the clients DB look with this approach, not to mention the size of the records in there... Does this method hurt my client when it comes to SEO? File Method If the DB method hurts my clients SEO and DB load I think I have to go with this method. It's a bit harder and I may have to tell them it will push the project back a bit. Other things to consider, the client is on a shared host, thats why i am concerned with DB load not to mention size. Don't worry about any other things, I've thought of them already and don't want to make this post a book, I'm just stuck on which method to go with. Please advise.... Quote Link to comment https://forums.phpfreaks.com/topic/89133-building-a-cms-need-answers-with-an-eye-towards-seo-and-db-load/ Share on other sites More sharing options...
trq Posted February 3, 2008 Share Posted February 3, 2008 I would go with the db method. If your using mysql, you really will not have any concerns over load. trust me, mysql can handle alot more than any website can throw at it. As for SEO, using mod_rewrite its easy enough to have your urls look like http://site.com/about/success_stories rather than http://site.com/about.php?get=success+stories Quote Link to comment https://forums.phpfreaks.com/topic/89133-building-a-cms-need-answers-with-an-eye-towards-seo-and-db-load/#findComment-456490 Share on other sites More sharing options...
s0c0 Posted February 3, 2008 Author Share Posted February 3, 2008 I don't even think about mod-rewrite lol. Thanks! Quote Link to comment https://forums.phpfreaks.com/topic/89133-building-a-cms-need-answers-with-an-eye-towards-seo-and-db-load/#findComment-457031 Share on other sites More sharing options...
tomfmason Posted February 3, 2008 Share Posted February 3, 2008 You can also increase performance by caching common queries. http://www.databasejournal.com/features/mysql/article.php/3110171 Quote Link to comment https://forums.phpfreaks.com/topic/89133-building-a-cms-need-answers-with-an-eye-towards-seo-and-db-load/#findComment-457082 Share on other sites More sharing options...
steviewdr Posted February 7, 2008 Share Posted February 7, 2008 Depending on the types of MySQL queries and the number of MySQL calls/selects on 1 page, this will determine if you are going to have problems or not. Wordpress which uses MySQL can easily bring down a Dual Quad Core 3ghz with 4gb of memory with a digg/slashdot. This is purely because, there could be 20-30 MySQL queries per page, depending on the number of widgets used etc. TBH - Your very much reinventing the wheel. There are LOADS of CMSs out there which are already built with SEO and performance in mind. Wordpress, gallery (caches a lot), drupal etc. Its just that its difficult to skin and setup them the way you want. Im looking towards typo3 for my CMS move. -steve Quote Link to comment https://forums.phpfreaks.com/topic/89133-building-a-cms-need-answers-with-an-eye-towards-seo-and-db-load/#findComment-460344 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.