Monday 03 March 2008 12:49:31 pm
Hi again,
>> should those 500000 records be attempted to be managed with that model? Would you go >> for that? Or would you choose some sort of integration or extension with dedicated DB
>> tables and interfaces? Looks like data management rather than content management >> project to me. Obviously, with that amount of data, a joint solution (ezp CMS + separate database) would be a good one. My suggestion (XML view of CMS-data) is not that efficient of course, but on the other side, it's quite easy to set up. If you want more control and a more efficient solution, then I would opt for an separate extension based on the API. Anyhow, I think the ezp-approach is a good one for projects like this. Where you have the classic needs for a CMS in combination with the need to provide access to and from just about any kind of database-systems. You need flexibility most of all. And that's, IMHO, what ezp is all about. Felix
Publlic Relations Manager
Greater Stavanger
www.greaterstavanger.com
|