Hi Betrand, ez is based on an EAV data-model (allowing us to store any new content-class without changing the DB schema). But it results in the the DBMS we currently use (e.g. MySQL, etc.) which is designed for more conventional relational database designs, having to work very hard to execute fetches. KV stores are designed for systems such as eZ and are able to execute the same types of queries but more efficiently than a system which would have expected different content classes to be in different tables. The current situation is convenient and very good for a system that allows new classes at any time. But in terms of efficiency on the DBMS, it's like creating a dbms on a dbms. So, using a KV store I would expect a performance improvement for fetches of maybe hundreds or thousands of percent. And scalability issues would be fully resolved.
I'm not sure how difficult it would be to adopt now as a storage engine. -- Luc. On 23 June 2010 14:26, Bertrand Dunogier <[email protected]> wrote: > Hello, > > 2010/6/23 Luc Chase <[email protected]> > > What plans are there to support the use of Key-Value ('KV') stores as a >> DBMS for eZ Publish? >> > This particular one hasn't been discussed as far as I know. Could you > elaborate on the benefits, and possibly the challenge it would represent > when it comes to integration ? > > -- > Bertrand > -- Luc. M. +44.7939 00 29 32 T. +44.2071939840 / +44.7040901582 Writing can be either readable or precise, but not at the same time. - Betrand Russell
-- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
