----- Original Message ----- From: "Jason Spisak" <444@hiretechs.com> To: "Sam Gendler" <sgendler@silcom.com> Cc: <zope@zope.org> Sent: Thursday, April 27, 2000 11:25 AM Subject: Re: [Zope] Zope's scalability across multiple web servers
Sam Gendler writes:
However, if you are dynamically creating objects in the ZODB (something that is strobly discouraged in a high volume write situation)
Why is that? I thought the connection overhead and maintainence of a RDBMS was a big deal? This gets brought up a lot. And I like to hear opinions. I am aware that whatever justification is given is purely about what works for you, but I'd love to hear the reasoning.
Actually, I think the ZODB is great. You wouldn't want to use it for a high overwrite situation (like a hit counter), but if you're *adding* things ZODB seems just fine. ZODB is really easy to work with and model things in. Philip & Ty's new SheetProvider stuff will help blur the lines between the ZODB and an RDBMS, too. If you have a few properties of an object that change frequently, just stick them on a property sheet that gets pulled from an RDBMS. Kevin