Hi there, To add my 2 cents, I have been looking into CouchDB in the last couple of weeks, and found this statement regarding Modeshape (Google "modeshape couchdb"):
http://modeshape.wordpress.com/2010/01/26/modeshape-isnt-your-fathers-jcr/ - "we envision lots of connectors, including connectors to ... document databases (like CouchDB and Cassandra)" See also: https://jira.jboss.org/browse/MODE-300 - Modeshape CouchDB issue (from 2008, low / non-existant activity) http://www.magnolia-cms.com/home/community/conference/2010/program/presentation-day/modeshape.html (slide 12) - Modeshape and Magnolia Greetings, Felix On Oct 13, 2010, at 3:45 PM, Unger, Richard wrote: > Hi Harold! > > About nosql: It isn’t clear to me what the benefits would really be. Allow me > to explain my point of view: > > JCR forms an important abstraction in Magnolia – consequently it is used in > many places. So replacing JCR would be a major amount of work, and the result > would be a Magnolia without storage abstraction, tied to a specific nosql > implementation. > > However, I think the storage abstraction is important to magnolia – JCR > presents to magnolia a hierarchical abstraction consisting of nodes and > properties. JCR is itself a “nosql” implementation (according to some > definitions, at least). JCR can use different backends to actually store the > data, including file-system, JDBC Databases and others. > > In my view the correct approach to attaching magnolia to a specific nosql > implementation is to create a Jackrabbit (JCR)-Backend for the nosql > database. Then magnolia will be able to use that nosql implementation, and no > changes to magnolia would be necessary. > > To improve magnolia’s performance (which, IMHO, is actually pretty good!) I > think it would be more useful to look at: > · Integrating Jackrabbit2 as the JCR implementation (Jackrabbit 2 is > supposed to be faster than Jackrabbit 1) > · Implementing paging in the tree-views in adminCentral (planned for > Magnolia 5?) – for nodes with many children (>100) > > Regards from Vienna, > > Richard Unger > > > > Von: [email protected] > [mailto:[email protected]] Im Auftrag von CAPITAINE Harold > Gesendet: Dienstag, 12. Oktober 2010 15:50 > An: [email protected] > Betreff: [magnolia-user] Magnolia with underlying no-sql database > > Hello devs, > > I would like to know if anyone of you has ever tried or even thinked about > using magnolia with an underlying no sql database, document oriented > architecture of course such as mangoDB or others, instead of JCR. This may be > a good solution to increase perfs? What do you think about this idea? > > Thanks in advance for you answers. > > CAPITAINE Harold > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
