Re: FN-FORUM: php, XML, content and searching

date posted 4th September 2007 09:07

Hi

You could still be using a main database for all the websites and pull
the data out of it into static XML files on a regular basis or when some
data is changed via your CMS and parse the XML remotely from each website.
I'd use PHP5 simpleXML methods and maybe some PEAR library for content
syndication, but I'm not sure what's your goal and which platform you're
on so it's just an idea.

Be good

Sam M - www.wiredeyes.com wrote:
>> -----Original Message-----
>>
>> On 4 Sep 2007, at 08:28, Sam M - www.wiredeyes.com wrote:
>>
>>
>>> Hi Guys
>>>
>>> Looking for some advice regarding using XML as a data source for
>>> website/s.
>>>
>>> Currently all site data for a site builder CMS I have developed is
>>> held in
>>> mySQL but I would prefer if it was stored in xml documents in the
>>>
>> file
>>
>>> system and so I could do away with the database as primary content
>>> data
>>> source.
>>>
>> Can you explain why you'd prefer a flat file based data storage
>> system over a relational database? especially as you go on to say:
>>
>> "The system would be used on 100's of websites at the same time"
>>
>> I'm not saying you're wrong or anything, just curious as to why
>> you're asking.
>>
>
> Not really about preference, it's more looking to better alternatives to
> using a database for site content or finding something more elegant.
>
> Firstly understand that this is for a CMS system that currently contains
> about 1000 published websites. Each user has their content stored in the
> database, data separated by userid/siteid, but I am getting the feeling that
> the mySQL database is going to become a bottleneck and want to pre-empt any
> major slowdown before it happens.
>
> Currently I'm using xml data stored in the database for elements such as the
> navigation but thought it might be a good idea to move that data out of
> mySQL and store it flat file (Each user has their own assets folders etc)
> and as far as I can see this would have a number of advantages.
>
> 1. Easy backup, user simply downloads their xml files and can re-upload them
> to restore their content.
> 2. A lot less database traffic, since the database would only be used for
> storing user and site profile information and billing info etc not mainly
> static website content.
> 3. Easy expansion, sites can be moved around from server to server easily.
> 4. Hopefully faster.
>
> Any other Q's or ideas?
>
>
>
>
>