OrientDB support

[lvca]

Hi,
I'd like to support OrientDB (http://www.orientechnologies.com) as a new implementation of Spring Data. OrientDB is a document-graph NoSQL dbms, so I don't know if it's better to implement the Document APIs or Graph APIs or maybe both.

Where can I start?

[trisberg]

Take a look at the MongoDB support as a start.

The Neo4j support is different in that it uses AspectJ and also supports cross-store persistence. It currently lacks a good Neo4jTemplate implementation for the lower level API support.

I would suggest starting with an OrientTemplate and would look at the MongoTemplate for ideas. Let us know how things work out.

-Thomas

[MichaelHunger]

Thomas,

> It currently lacks a good Neo4jTemplate implementation for the lower level API support.

This is not quite true, the Neo4jTemplate covers all the low level operations in a convenient API for Spring Developers.

Cheers

Michael

[trisberg]

Hi Michael,

Yes, the Neo4j template style support has changed since December and it now does have some of this lower level support.

Cheers,
Thomas

[pabloa]

Cool! Do you have news about OrientDB Support for Spring Data?

[ambeth]

Resurrecting this thread for two reasons:

1) I'd like to register my interest for orientDB Spring-Data support
2) I'd like to hear if anyone has made any efforts on this

[Musashi]

Ciao Luca,
Any hope to see this spring data working? i have a neo4j project i would like to port to orient and is using data, i see now this is the only advantage neo4j takes now.

may congrats to 1.0,

let's this baby rox

have a nice day

[lvca]

Hi all,
I'm seriously interested in the development of this implementation for OrientDB. Now, I'd like to have both Document and Graph templates. Probably the simpler is the Document one. WDYT? Anyone is interested on this task?

Lvc@
CEO NuvolaBase - the OrientDB company

[flatif]

I would create an OrientDocumentTemplate and OrientGraphTemplate (with their repositories, annotations and mapping, ecc).

The implementation of the document based API could be based on the mongoDB implementation since the core functionality of both DBs are similar, however spring data modules only share the basic infrastructure of spring-data-commons so one would have to create all the document-database APIs from scratch, however, some code could actually be the same and in fact, even the basic design could be the same as well (and I think it should, it would be a waste of time to rewrite everything from scratch having well designed apache licensed code available, and if some improvements are made along the way, the mongo implementation could benefit from it too)

[lvca]

Hi,
+1 about using MongoDB as beginning to design and develop the OrientDocumentTemplate. Probably the Graph one is more complex, but I'm pretty sure once the Document is ready writing the Graph module will be straightforward.

The big big good point of OrientDB in comparison to MongoDB is that OrientDB is written in Java! This means SpringData users could
the OrientDB's "local" mode to use it embedded in the same JVM of the applications for the maximum of the performance.

Lvc@
CEO NuvolaBase - the OrientDB company