I ended up choosing OrientDB because: * Part of my data model was very painful with a traditional SQL database, whereas graphs work nicely. * Parts of my data model very much like the Document DB aspects of Orient - especially the EMBEDDED* types. * Licensing is good * The various query/fetching methods - SQL dialect, gremlin, direct object load, etc, map to various ways I think about accessing my data. * The times I want to enforce schema, I can, which gives me a certain level of type-safe comfort I enjoy.
The reason I chose against Neo4j was mostly licensing, the above is just a nice benefit. A couple of Orient cons from my POV: * When working in a non-jvm language, it somewhat painful to use the binary or http interfaces. The http interface feels a bit inconsitent, and arbitrary when it comes to return values, and what can and cannot be done, rather than a full API. e.g. I use python, and interfacing with full features is just frustrating sometimes (and bulbflow/rexster don't really allow me to use everything fully) * Some things are non-intuitive in the "Orient way of doing things", and it's taken a lot of experimenting to get things done sometimes. Being a small community still, not every question I have is answered by a simple google search. HTH On Thursday, January 5, 2012 11:56:14 PM UTC-6, Luanne Misquitta wrote: > > Hi everyone, > > Did any of you consider using neo4J and why did you pick OrientDB over it? > > Thanks > Luanne > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
