[Zope] Hardware for Zope + ZEO

[Mario Valente]

At 15:36 31-01-2003 +0900, Wankyu Choi wrote:
>From: Mario Valente [mailto:mvalente@ruido-visual.pt] 
>Sent: Wednesday, January 29, 2003 10:38 PM
>To: Wankyu Choi; zope@zope.org
>Subject: Re: [Zope] Hardware for Zope + ZEO
>
>>>  Use this as your backend server (MySQL + ZEO). Use BerkeleyDB or
>DirectoryStorage. You should only store in Zope what is "Zope stuff" (DTML
>methods, Python methods, ZClasses, ZSQL queries, etc). All the original
>site data should be kept in MySQL. All images should be stored as External
>Files (as well as any other BLOBs like PDF files, DOC files, etc).
>
>which means... you wouldn't put any serious heavy-weight data into your ZODB
>storage no matter how good it might be? 
>

>Plus, I rewrote all the CMF content types to add extra features and stuff.
>Now I'll need to do the same with these content types to make use of MySQL.
>
>Is my assumption right? That makes ZODB look like a metadata holder, not a
>database :(
>

  The ZODB is an object-oriented database. It should be used to store
 object oriented data (especially data that depens on hierarchical relations
 and on inheritance). The ZODB shouldnt be used to store structured tabular
 data; for that you should use a relational database management system.

  Its just a question of using the right tools for the problem. I wouldn store
 binary files neither in the ZODB or in a relational database; likewise I
wouldnt
 put text files/fields either into the ZODB or a relational database
(altough in
 Zope, using ZCatalog or NGTextIndex to index text, it wouldnt be so bad).

  C U!

  -- Mario Valente