Received Sat, 15 Mar 2008 20:07:45 PHT
CMS / MySQL web site or flat file web site - what is better or more stable ? Here my recommendation for your site mode
The recent downtime of all MySQL related online services such as my Blog, Philippine islands photo gallery and my postfix using a MySQL dbase as well has clearly shown how fragile a CMS can be.
Downtime means loss of traffic, possible loss of SERPS on major search engines resulting in prolonged loss of advertising revenue as a result of decreased overall traffic ......
Above all downtime causes loss of revenue - without cash no work possible. To publish on professional level costs a little fortune in investment of time, SW, HW and other expenses. Hence downtime always is a painful loss that needs to be avoided at any cost.
My major traffic all is on flat files. ALL spiritual chapters and teachings of love are flat files. Anything of true and lasting spiritual value is flat files. To create and maintain Blog and Photo Gallery definitely has cost a 5 digit $ amount in total expenses. But while all these files are important, at least there is no severe spiritual damage when some of these content pages are temporarily down.
The conclusion is clearly that all truly important information should be published on flat files!
Typically all CMS systems such as blogs, galleries or other content management systems are quiet complex - normally too complex to be fully controlled and bug-fixed by an average publisher. Hence in severe problems with a CMS using MySQL or other db's - you always may depend on other people as a resource of help. Last night again has shown that in real emergencies there is no one online who could help. Hence you entirely depend on what you can and know to solve all on your own!
It always was my philosophy to publish all truly helpful and important topics in flat file. Even if that means more time needed to publish and promote. Yesterday's downtime showed that all normal traffic was continuing. Only a few thousand visitors got lost as site readers during the approx 12+ hrs of MySQL downtime. Hence also the loss in advertisement revenue was limited. Having had approximately 140'000-150'000 PHP of charity expenses during the last 30 days requires a steady in-flow as well. Nobody can satisfy its thirst and hunger from an empty glass.
Thus if you plan a web site and hopefully have some real important and valuable information and expertise to share, then I clearly recommend you use flat files.
In addition to a.m. stability reasons, any CMS also may imply a smaller or rather greater additional security risk for your entire site and server. This latter point is most important to me. A secure and tight server let's me sleep fine whenever I rest and work fully concentrated when ever work is due.
A combination of flat files for all truly important content and a MySQL driven CMS for all blog and temporary content may be an ideal option. The main content of your site however should be large enough in volume, quality and traffic to fully assure your server and web publishing activities in case of down-times. Your revenue assuring content always should be rock solid and stable - it should be the foundation of your life!
Love and bliss
hans




