topic Re: Using NoSQL Instead of RDBMS in Alfresco Archive

Using NoSQL Instead of RDBMS

kylesaid — Fri, 21 Jan 2011 13:32:57 GMT

I know this wouldnt be trivial, but how feasible would it be to rip out the RDBMS replace it with a NoSQL database? Specifically graph databases like Neo4j work very well for ECM use cases. Any thoughts?

Re: Using NoSQL Instead of RDBMS

kylesaid — Fri, 28 Jan 2011 14:20:52 GMT

**Bump** No Interest?

Here's a link for an intro to Neo4j. It's an 8-page into that describes a high-level architectural view and a big of history behind the product.
http://dist.neo4j.org/neo-technology-introduction.pdf

Its interesting that Neo4j's first incarnation originated from the need for a high performance and highly scalable engine for an ECM implementation.

Re: Using NoSQL Instead of RDBMS

mrogers — Fri, 28 Jan 2011 14:55:36 GMT

Yours is a big question, so please don't take a lack of answer to mean there's no interest. The problem is where to start …

There's clearly some overlap between the functionality provided by the alfresco repository and a NoSql implementation like Neo4j.
On one hand its very difficult to "rip out the database" for all use cases for Alfresco..

Adding a NoSql store to Alfresco could makes a lot of sense for some intermediate use cases. And in particular some WCM scenarios we have worked though have NoSql databases as a "delivery" tier.

Re: Using NoSQL Instead of RDBMS

kylesaid — Fri, 28 Jan 2011 15:38:15 GMT

I'd most likely want to co-locate a Neo4j database along side the RDBMS for starters. Content, folders, users, security roles are all nodes and CRUD operations are the relationships between those nodes. Using Spring AOP advices, I dont see a huge amount of effort for creating a graph network. I just wouldnt know what classes or methods to intercept using said advices.

Rendering all of this in Share is a whole different beast, but I would at the very least like to get the backend basics down. The basics being a graph network of content and folders nodes and the relationships in between.

Can anyone narrow down what packages I should look at for the existing persistence layer?

Re: Using NoSQL Instead of RDBMS

huima — Wed, 11 May 2011 12:54:28 GMT

This is actually really interesting question and funny that there are no more discussions about Neo4J in the Alfresco forums 😄

I just stumbled upon Neo4J as I am designing / thinking about designing a system, where Alfresco could / would be used as a document storage and additional data would come from multiple relational databases and systems. Modeling everything in relational database with ORM tools would / could be slow and cumbersome, compared to the models offered by Neo4j and Alfresco. As there can be problem traversing Alfresco's graph ( as associations are not indexed in Lucene ), building and maintaining search graph in Neo4J could be a good idea in some cases.

Definitely would be interested to hear experiences, if someone has done anything with Alfresco and Neo4J.

Re: Using NoSQL Instead of RDBMS

kylesaid — Wed, 11 May 2011 14:34:14 GMT

I've decided that i'm going to start simple and i'm going to create a bolt-on for a Neo4j-Alfresco Auditing GraphDB. All of the logic for creating the nodes and relationships are pretty straight forward. Adding the Alfresco nodes and relationships to the Neo4j Lucene indexes should be pretty trivial as well. I'm already seeing EXTREMELY positive results from queries that would traditionally have poor performance characteristics in which 100s/millions rows data set with lots of joins would take minutes. Neo4j is traversing and returning results from said data set in a few seconds. Once I have something crude put together i'll share in more detail.

This really solves a whole lot of issues that I can see.
- Working with semi-structured or unstructured data
- Object-relational impedance mismatch. No need for ORM tools as you already mentioned.
- Working with large volume data sets
- Working with varied and complex data sets. 100s of joins needed? No Problem!
- Ease of handling evolving schemas. We all know that business requirements never remain static, so this is VERY important.

One of my colleagues asked me why not use a NOSQL document db or a key-value store. My answer was simple, a graph database offers the richest data model and give me the added benefit traversing (or joining) by relationship. Also while k-v stores can handle a larger data set at the moment, Neo4j can still handle 10s of billions of nodes within a single JVM. Lastly, k-v stores are absolutely horrible for developer productivity, whereas working with Neo4j feels very natural. That also includes columnar-family db's like Apache Cassandra.

Re: Using NoSQL Instead of RDBMS

kylesaid — Wed, 11 May 2011 14:48:19 GMT

Here's a good presentation btw….

http://www.mefeedia.com/watch/31077078

Re: Using NoSQL Instead of RDBMS

zoe — Mon, 14 May 2012 20:41:20 GMT

I've decided that i'm going to start simple and i'm going to create a bolt-on for a Neo4j-Alfresco Auditing GraphDB. … Once I have something crude put together i'll share in more detail.

I'm interested in hearing about this - are you still planning on sharing the details? Would love to see it!
Zoe

Re: Using NoSQL Instead of RDBMS

lucasalberto — Fri, 08 May 2015 20:44:25 GMT

Are there news about this topic, nosql + alfresco?